public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/47896] wrong code with -O -fno-early-inlining -fipa-pta -fno-tree-dominator-opts -fno-tree-forwprop Date: Sat, 26 Feb 2011 23:28:00 -0000 [thread overview] Message-ID: <bug-47896-4-HMbcpRALfJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47896-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47896 --- Comment #1 from Zdenek Sojka <zsojka at seznam dot cz> 2011-02-26 23:16:32 UTC --- Created attachment 23481 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23481 reduced testcase $ g++ -O -fno-early-inlining -fipa-pta -fno-tree-dominator-opts -fno-tree-forwprop pr47896.C $ ./a.out Aborted At the assembly level, the problematic line seems to be: mov DWORD PTR [rsp+32], 9 # i9, which directly stores the constant 9, instead of the updated value 8. It doesn't seem to crash when compiled as C code.
next prev parent reply other threads:[~2011-02-26 23:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-25 19:24 [Bug tree-optimization/47896] New: " zsojka at seznam dot cz 2011-02-26 23:28 ` zsojka at seznam dot cz [this message] 2011-02-27 15:13 ` [Bug tree-optimization/47896] " rguenth at gcc dot gnu.org 2011-03-01 12:50 ` 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-47896-4-HMbcpRALfJ@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).