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/49768] C99 style union initializations does not work as expected with optimizations
Date: Sun, 17 Jul 2011 18:23:00 -0000 [thread overview]
Message-ID: <bug-49768-4-tFbnOuOJ5V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49768-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49768
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org,
| |mikpe at it dot uu.se
--- Comment #2 from Mikael Pettersson <mikpe at it dot uu.se> 2011-07-17 18:22:21 UTC ---
It started with r164688:
Author: hubicka
Date: Tue Sep 28 16:28:39 2010
New Revision: 164688
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=164688
Log:
* tree-ssa-ccp.c (fold_ctor_reference): New function.
(fold_const_aggregate_ref): Use it.
* fold-const.c (canonicalize_constructor_val): Check that we don't fold
into external static.
The dumps from r164687 and r164688 start to differ in pr49768.c.061t.ccp2, when
r164688 removes the runtime check and the static object, and makes the abort()
call unconditional.
Removing the unused initial padding bit field unbreaks the test case.
next prev parent reply other threads:[~2011-07-17 18:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 10:41 [Bug c/49768] New: " vrahkone at gmail dot com
2011-07-17 12:47 ` [Bug c/49768] " mikpe at it dot uu.se
2011-07-17 18:23 ` mikpe at it dot uu.se [this message]
2011-07-17 22:01 ` [Bug c/49768] [4.6/4.7 Regression] " jakub at gcc dot gnu.org
2011-07-17 22:11 ` jakub at gcc dot gnu.org
2011-07-18 8:48 ` rguenth at gcc dot gnu.org
2011-07-18 12:48 ` [Bug tree-optimization/49768] " jakub at gcc dot gnu.org
2011-07-19 9:24 ` jakub at gcc dot gnu.org
2011-07-19 9:41 ` jakub at gcc dot gnu.org
2011-07-19 9:42 ` jakub at gcc dot gnu.org
2011-08-04 13:45 ` vrahkone at gmail dot com
2011-08-24 10:37 ` 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-49768-4-tFbnOuOJ5V@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).