David MacKenzie 010877137c * Makefile.in (BFD_LIBS, ALL_MACHINES, BFD32_BACKENDS, BFD64_BACKENDS,
OPTIONAL_BACKENDS): Alphabetize entries and add a few missing ones.
	* archures.c: Alphabetize decls.
1993-08-19 21:07:50 +00:00
..
1993-08-09 20:31:30 +00:00
1991-05-18 02:58:02 +00:00
1991-05-18 02:58:02 +00:00
1993-08-09 19:25:56 +00:00
1992-02-21 22:54:39 +00:00
1993-08-19 19:45:23 +00:00
1991-03-21 21:11:25 +00:00
1993-04-24 02:10:09 +00:00
1993-02-04 20:59:55 +00:00
1991-10-01 03:43:11 +00:00
1991-10-01 03:43:11 +00:00
1991-10-01 03:43:11 +00:00
1991-10-25 07:16:56 +00:00
1991-10-01 03:43:11 +00:00
1992-08-25 22:04:53 +00:00
1991-05-18 02:58:02 +00:00
1993-06-02 21:24:35 +00:00
1993-04-29 15:48:35 +00:00
1991-12-18 23:01:07 +00:00
1993-06-02 20:24:22 +00:00
1993-08-17 22:50:20 +00:00
1991-10-01 03:43:11 +00:00
1993-06-16 01:51:56 +00:00
1993-06-22 03:22:54 +00:00
1993-07-22 23:09:07 +00:00
1993-08-07 22:45:02 +00:00
1993-08-05 18:24:21 +00:00
1991-11-22 04:59:56 +00:00
1993-08-07 22:38:22 +00:00
1993-07-11 23:23:20 +00:00
1993-05-17 19:03:44 +00:00

HPPA/ELF README file:

	HP PA-RISC support was contributed by the Center for Software Science
	at the University of Utah.

This is the status of the hppa/elf code in bfd 2.0 as of January 29, 1993:

1. It generates correct ELF files for all of the input I've given it
so far.  I've used this version of libbfd.a to build an hppa/elf
version of gas 1.36 (emits SOM).  I've run files as large as 200K
lines of assembly through it.

2. ELF executables that are created *always* have 3 program header
table entries.  This is due to the exec() support we have in the
kernel for ELF executables.  It expects *exactly* 3 program header
table entries -- one for text, one for data, and one for bss.
Currently, there's no support for any other types of program header
table entries.