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 middle-end/36075] [4.3.1 Regression] FAIL: gcc.c-torture/execute/20021119-1.c execution, -O2 Date: Fri, 09 May 2008 21:11:00 -0000 [thread overview] Message-ID: <20080509211101.26204.qmail@sourceware.org> (raw) In-Reply-To: <bug-36075-276@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2008-05-09 21:11 ------- Ping. As the testcase in question is really simple some analysis is appreciated. On i686 the testcase is optimized to return 0 via inlining with the very first CCP pass at -O2. So I don't see how this can fail at all. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36075
next prev parent reply other threads:[~2008-05-09 21:11 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-29 3:11 [Bug middle-end/36075] New: " danglin at gcc dot gnu dot org 2008-04-29 11:31 ` [Bug middle-end/36075] " rguenth at gcc dot gnu dot org 2008-05-09 21:11 ` rguenth at gcc dot gnu dot org [this message] 2008-05-09 21:26 ` rguenth at gcc dot gnu dot org 2008-05-09 21:56 ` danglin at gcc dot gnu dot 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=20080509211101.26204.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).