public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/37868] [4.3 Regression] code that breaks TBAA is misoptimized even with -fno-strict-aliasing Date: Thu, 20 Nov 2008 12:28:00 -0000 [thread overview] Message-ID: <20081120122654.25633.qmail@sourceware.org> (raw) In-Reply-To: <bug-37868-15165@http.gcc.gnu.org/bugzilla/> ------- Comment #10 from rguenth at gcc dot gnu dot org 2008-11-20 12:26 ------- Subject: Bug 37868 Author: rguenth Date: Thu Nov 20 12:25:26 2008 New Revision: 142041 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142041 Log: 2008-11-20 Richard Guenther <rguenther@suse.de> PR tree-optimization/37868 * gcc.dg/torture/pr37868.c: New testcase. * gcc.c-torture/execute/pr38048-1.c: Likewise. * gcc.c-torture/execute/pr38048-2.c: Likewise. Added: trunk/gcc/testsuite/gcc.c-torture/execute/pr38048-1.c trunk/gcc/testsuite/gcc.c-torture/execute/pr38048-2.c trunk/gcc/testsuite/gcc.dg/torture/pr37868.c Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37868
prev parent reply other threads:[~2008-11-20 12:28 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-18 18:17 [Bug tree-optimization/37868] New: code that doesn't " edwintorok at gmail dot com 2008-10-18 18:30 ` [Bug tree-optimization/37868] code that " sabre at nondot dot org 2008-10-18 18:58 ` rguenth at gcc dot gnu dot org 2008-10-18 22:36 ` rguenth at gcc dot gnu dot org 2008-10-18 22:44 ` rguenth at gcc dot gnu dot org 2008-10-22 11:48 ` [Bug tree-optimization/37868] [4.3 Regression] " rguenth at gcc dot gnu dot org 2008-10-22 13:50 ` rguenth at gcc dot gnu dot org 2008-11-03 11:29 ` jakub at gcc dot gnu dot org 2008-11-07 12:51 ` rguenth at gcc dot gnu dot org 2008-11-20 12:14 ` rguenth at gcc dot gnu dot org 2008-11-20 12:15 ` rguenth at gcc dot gnu dot org 2008-11-20 12:28 ` rguenth at gcc dot gnu dot org [this message]
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=20081120122654.25633.qmail@sourceware.org \ --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).