From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: sje@cup.hp.com (Steve Ellcey)
Cc: wilson@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: HP-UX IA64 Patch to fix earlier patch
Date: Fri, 15 Nov 2002 17:00:00 -0000 [thread overview]
Message-ID: <200211160100.gAG10FED015986@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <200211152348.PAA26381@hpsje.cup.hp.com> from "Steve Ellcey" at Nov 15, 2002 03:48:36 pm
> > From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
> >
> > I agree with Jim here. Not too long ago, I used this technique to avoid
> > defining FUNCTION_ARG_REG_LITTLE_ENDIAN on the hppa64 port. I also
> > managed to fix a long standing bug in the 32-bit port passing small
> > structs using the same technique. Jim's comment is an over simplification
> > of what really happens when a DImode value is used in a PARALLEL on
> > big-endian 32-port. You actually get right-justified data in this case.
> > See function_arg and function_arg_padding in pa.c.
>
> I'll give this a try. Do you know if this behavour keys off of
> WORDS_BIG_ENDIAN, BYTES_BIG_ENDIAN, or BITS_BIG_ENDIAN? On PA HP-UX all
> of these are 1, but on IA64 HP-UX we are setting BYTES and WORDS to 1
> and leaving BITS at 0. Setting BITS_BIG_ENDIAN to 1 was causing some
> problems that I don't recall off the top of my head.
emit_group_load and emit_group_store use extract_bit_field and
store_bit_field. They don't directly key off any of the above
but extract_bit_field and store_bit_field do.
In the 32-bit port, we had the rather unique situation where 5-8 byte
structs needed to be right-justified in the same manner as 1-4 byte
structs. Structs larger than this are left justified.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next prev parent reply other threads:[~2002-11-16 1:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200211150002.gAF021fD013288@hiauly1.hia.nrc.ca>
2002-11-15 15:48 ` Steve Ellcey
2002-11-15 17:00 ` John David Anglin [this message]
2002-11-15 17:38 ` Jim Wilson
2002-11-06 14:01 Steve Ellcey
2002-11-14 10:37 ` Jim Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200211160100.gAG10FED015986@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=sje@cup.hp.com \
--cc=wilson@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).