public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/49119] PowerPC: Wrong code with designated initializers and bit fields
Date: Mon, 22 Aug 2011 16:44:00 -0000 [thread overview]
Message-ID: <bug-49119-4-k438ELK6UU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49119-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49119
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #3 from Mikael Pettersson <mikpe at it dot uu.se> 2011-08-22 16:40:35 UTC ---
I can't reproduce the wrong code on powerpc64-linux (with -m32), or on
m68k-linux (also big-endian, assuming it's an endianess issue) with
gcc-4.6.2-recentish.
How exactly was your gcc configured, and how did you invoke it on this test
case?
Also please inspect the generated assembly code (gcc -S) rather than
disassembled object code (objdump -d). Disassembly tends to omit relocation
data.
next prev parent reply other threads:[~2011-08-22 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 8:29 [Bug c/49119] New: " sebastian.huber@embedded-brains.de
2011-05-23 8:23 ` [Bug c/49119] " sebastian.huber@embedded-brains.de
2011-08-22 13:23 ` sebastian.huber@embedded-brains.de
2011-08-22 16:44 ` mikpe at it dot uu.se [this message]
2011-08-23 15:27 ` sebastian.huber@embedded-brains.de
2011-08-24 8:30 ` sebastian.huber@embedded-brains.de
2011-08-24 10:34 ` mikpe at it dot uu.se
2011-08-24 10:36 ` sebastian.huber@embedded-brains.de
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-49119-4-k438ELK6UU@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).