public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/34010] [4.8/4.9/5 Regression] ppc64 bad stdargs codegen for zero sized objects
Date: Thu, 12 Mar 2015 17:38:00 -0000 [thread overview]
Message-ID: <bug-34010-4-HuvKyuULtV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-34010-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34010
Aldy Hernandez <aldyh at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
CC| |aldyh at gcc dot gnu.org
--- Comment #7 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
>From Mike's comment I see this should fail on ppc -m64, however on ppc64-linux
I see:
[aldyh@gcc1-power7 gcc]$ make check-gcc RUNTESTFLAGS=struct-layout-1.exp
...
=== gcc Summary ===
# of expected passes 140
[aldyh@gcc1-power7 gcc]$ make check-g++ RUNTESTFLAGS=struct-layout-1.exp
...
=== g++ Summary ===
# of expected passes 150
Is this still an issue, is this only visible on darwin and/or mips, or is there
another way to reproduce the problem?
next prev parent reply other threads:[~2015-03-12 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-34010-4@http.gcc.gnu.org/bugzilla/>
2012-02-01 23:02 ` [Bug middle-end/34010] [4.4/4.5/4.6/4.7 " pinskia at gcc dot gnu.org
2012-02-03 9:33 ` jakub at gcc dot gnu.org
2012-03-13 14:17 ` [Bug middle-end/34010] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 12:28 ` rguenth at gcc dot gnu.org
2013-04-12 15:17 ` [Bug middle-end/34010] [4.7/4.8/4.9 " jakub at gcc dot gnu.org
2014-06-12 13:45 ` [Bug middle-end/34010] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:28 ` [Bug middle-end/34010] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-03-12 17:38 ` aldyh at gcc dot gnu.org [this message]
2015-03-17 22:45 ` aldyh at gcc dot gnu.org
2015-03-17 23:34 ` mrs at gcc dot gnu.org
2015-03-18 0:06 ` aldyh at gcc dot gnu.org
2015-03-18 18:44 ` segher at gcc dot gnu.org
2015-04-03 6:31 ` [Bug middle-end/34010] [4.8/4.9 " amker at gcc dot gnu.org
2015-06-23 8:22 ` rguenth at gcc dot gnu.org
2015-10-16 8:24 ` [Bug middle-end/34010] [4.9 " rguenth at gcc dot gnu.org
2015-10-16 17:46 ` mrs at gcc dot gnu.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=bug-34010-4-HuvKyuULtV@http.gcc.gnu.org/bugzilla/ \
--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).