public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/58096] [4.9 Regression] gcc.dg/tree-ssa/attr-alias.c fails with r201439 Date: Tue, 27 Aug 2013 16:55:00 -0000 [thread overview] Message-ID: <bug-58096-4-0hWqi4nwLg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58096-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58096 Bernd Edlinger <bernd.edlinger at hotmail dot de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernd.edlinger at hotmail dot de --- Comment #5 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- Created attachment 30706 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30706&action=edit proposed patch This is probably not really a bug in the compiler. Obviously the -fdump-tree-optimized format was changed, and the test case should be adapted to not expect a space after test4: ;; Function main (main, funcdef_no=1, decl_uid=1372, symbol_order=4) (executed once) main () { <bb 2>: test (); test4.localalias.0.localalias.2 (); [tail call] return; } The test case is inconsistent, because the comment mentions test1 and test2 can be optimized away, and the scan-tree-dump-not statements search for test1 and test2, but there is no test1 in the source code.
next prev parent reply other threads:[~2013-08-27 16:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-06 21:07 [Bug other/58096] New: " pthaugen at gcc dot gnu.org 2013-08-06 23:33 ` [Bug middle-end/58096] [4.9 Regression] " dje at gcc dot gnu.org 2013-08-09 12:45 ` ro at gcc dot gnu.org 2013-08-12 6:17 ` yufeng at gcc dot gnu.org 2013-08-19 22:36 ` hp at gcc dot gnu.org 2013-08-27 16:55 ` bernd.edlinger at hotmail dot de [this message] 2013-09-04 2:00 ` hp at gcc dot gnu.org 2013-09-04 21:50 ` pthaugen at gcc dot gnu.org 2013-09-05 19:40 ` hubicka 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-58096-4-0hWqi4nwLg@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).