public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15941] [3.4/3.5 regression] new fails gcc.dg/compat/struct-by-value-11 and gcc.dg/compat/struct-by-value-1
Date: Sat, 12 Jun 2004 20:43:00 -0000 [thread overview]
Message-ID: <20040612204331.18129.qmail@sourceware.org> (raw)
In-Reply-To: <20040611160703.15941.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2004-06-12 20:43 -------
Subject: Re: [3.4/3.5 regression] new fails gcc.dg/compat/s
> > The 32-bit PA ABI has rather special requirements for passing 5-7 byte
> > structs. See the comment in function_arg in pa.c. I believe the fail
> > in test5 is caused by trying to pass a 5 byte struct.
>
> So is the PA FUNCTION_ARG_BOUNDARY function lying about the alignment?
Well, it's not defined so how could we be lying ...
The default is clearly wrong. We seem to have been depending on
MAX_PARM_BOUNDARY which appears to be a relic.
Let me see if defining FUNCTION_ARG_BOUNDARY helps.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15941
next prev parent reply other threads:[~2004-06-12 20:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 16:07 [Bug c/15941] New: [regression 3.4.1] " danglin at gcc dot gnu dot org
2004-06-11 16:29 ` [Bug target/15941] [3.4 regression] " pinskia at gcc dot gnu dot org
2004-06-11 16:45 ` giovannibajo at libero dot it
2004-06-11 16:59 ` mmitchel at gcc dot gnu dot org
2004-06-11 20:52 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-11 20:55 ` [Bug target/15941] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-06-11 21:26 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-12 16:13 ` danglin at gcc dot gnu dot org
2004-06-12 19:02 ` rth at redhat dot com
2004-06-12 20:43 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-06-12 21:37 ` dave at hiauly1 dot hia dot nrc dot ca
2004-06-18 2:48 ` danglin at gcc dot gnu dot org
2004-06-18 4:06 ` danglin at gcc dot gnu dot org
2004-06-18 19:41 ` rth at gcc dot gnu dot org
2004-06-19 17:49 ` mmitchel at gcc dot gnu dot org
2004-06-19 19:25 ` cvs-commit at gcc dot gnu dot org
2004-06-19 19:49 ` cvs-commit at gcc dot gnu dot org
2004-06-19 19:50 ` danglin at gcc dot gnu dot org
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=20040612204331.18129.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).