public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/58794] [4.8/4.9 Regression] ICE in set_lattice_value, at tree-ssa-ccp.c:455 on x86_64-linux-gnu (at -O1, -O2, and -O3) Date: Mon, 21 Oct 2013 11:38:00 -0000 [thread overview] Message-ID: <bug-58794-4-vNyoXOTi2c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58794-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58794 --- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > I'm sure that we can build such FIELD_DECL only with Ada though, so, Eric, > can you provide a testcase where that happens - thus, that shows that > side-effects cannot be ignored here by for example comparing > &f.x and &f.x for a case where that is not equal? I think we need to > concern ourselves only with mutating side-effects, not a volatile load. I don't think so, we do not rely on expressions appearing in offsets or sizes to implement the semantics of the language, that would be too error-prone; instead these expressions are computed once for all when the type is elaborated. > The question is whether the patch is ok as-is or if I have to make > behavior dependent on is_gimple_form (ugh). A testcase that breaks > if not guarding it that way would be nice to have (I'll check if anything > existing triggers). Go ahead I'd say.
next prev parent reply other threads:[~2013-10-21 11:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-18 18:41 [Bug tree-optimization/58794] New: " su at cs dot ucdavis.edu 2013-10-21 8:42 ` [Bug tree-optimization/58794] [4.8/4.9 Regression] " rguenth at gcc dot gnu.org 2013-10-21 10:03 ` rguenth at gcc dot gnu.org 2013-10-21 11:38 ` ebotcazou at gcc dot gnu.org [this message] 2013-10-21 13:33 ` rguenth at gcc dot gnu.org 2013-10-21 13:34 ` [Bug tree-optimization/58794] [4.8 " rguenth at gcc dot gnu.org 2013-11-18 15:15 ` rguenth 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-58794-4-vNyoXOTi2c@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: linkBe 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).