This is the mail archive of the
mailing list for the GCC project.
Re: Deprecate 32-bits HP-PA for GCC 4.8?
- From: John David Anglin <dave dot anglin at bell dot net>
- To: Jeff Law <law at redhat dot com>
- Cc: Steven Bosscher <stevenb dot gcc at gmail dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, John David Anglin <danglin at gcc dot gnu dot org>
- Date: Mon, 07 May 2012 14:25:08 -0400
- Subject: Re: Deprecate 32-bits HP-PA for GCC 4.8?
- References: <CABu31nPBjtp4h+LpVTDkLjPE=9dm3auxCyk6LjHTaCQADxB3xg@mail.gmail.com> <4FA8099B.firstname.lastname@example.org>
On 5/7/2012 1:42 PM, Jeff Law wrote:
On 05/07/2012 11:33 AM, Steven Bosscher wrote:
There is also a 32-bit netbsd port that a limited number of users are
Hello,No objections from me. PA1.x machines are ancient. However, before
making the decision, I think making sure your facts are correct would
GCC is well into stage 1 for GCC 4.8, but I haven't seen any proposals
for targets to be deprecated. I have one I would like to put on the
list, so here's something to start a discussion with:
Deprecate all support for 32-bits HP-PA. This includes HP-UX10, and
PA-7000 and older.
PA linux runs on both PA 1.1 and 2.0 machines. The runtime is 32-bit.
Kernels can be either
Does the PA linux port run on the older PA machines or did they
restrict themselves to PA2.0 and newer? I certainly recall them
working on 32bit ports at one time.
3. The PA-7000 series only run HP-UX 10 or earlier, so support for
HP-7000 and older is pointless without HP-UX10 support.
32-bit or 64-bit.
I believe this is correct. The capability to generate 1.0 code could be
Well, there was a PA ELF 32 bit target, but I suspect that code has
long since died.
4. 32-bits HP-PA uses the SOM binary object format, i.e. it is a
non-ELF target (64-bits HP-PA is ELF).
IIRC TARGET_PA_11 was implicitly on when compiling 2.0 support.
Again, worth checking since it may affect how much code you think you
can clean up.
Removing support for anything older than PA-8000 results in a
considerable cleanup for the PA architecture: ~3300 lines out of
~23000, estimated by cleaning all "!TARGET_64BIT" and "TARGET_PA_11"
patterns in pa.md and pa.c, and most of the cleanups to remove support
for SOM objects.
Personally, I don't think the effort is worth it and would prefer to
spend my time working
on new features like movmisalign support.
John David Anglin email@example.com