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/42512] [4.5 Regression] integer wrong code bug with loop Date: Fri, 08 Jan 2010 16:53:00 -0000 [thread overview] Message-ID: <20100108165328.25536.qmail@sourceware.org> (raw) In-Reply-To: <bug-42512-12544@http.gcc.gnu.org/bugzilla/> ------- Comment #8 from rguenth at gcc dot gnu dot org 2010-01-08 16:53 ------- It FAILs FAIL: gcc.dg/vect/pr36630.c scan-tree-dump-times vect "vectorized 1 loops" 1 but otherwise passes testing. I'll see what effect it has on SPEC 2006 and investigate the above. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42512
next prev parent reply other threads:[~2010-01-08 16:53 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-26 19:27 [Bug c/42512] New: possible integer wrong code bug regehr at cs dot utah dot edu 2009-12-26 20:00 ` [Bug middle-end/42512] [4.5 Regression] integer wrong code bug with loop jakub at gcc dot gnu dot org 2009-12-26 22:13 ` hjl dot tools at gmail dot com 2009-12-26 22:16 ` hjl dot tools at gmail dot com 2009-12-27 14:43 ` ebotcazou at gcc dot gnu dot org 2010-01-08 14:07 ` rguenth at gcc dot gnu dot org 2010-01-08 15:00 ` rguenth at gcc dot gnu dot org 2010-01-08 16:20 ` spop at gcc dot gnu dot org 2010-01-08 16:53 ` rguenth at gcc dot gnu dot org [this message] 2010-01-08 17:07 ` rguenth at gcc dot gnu dot org 2010-01-08 17:21 ` rguenth at gcc dot gnu dot org 2010-01-08 17:55 ` Sebastian Pop 2010-01-08 17:55 ` sebpop at gmail dot com 2010-01-09 12:04 ` rguenth at gcc dot gnu dot org 2010-01-09 12:04 ` rguenth at gcc dot gnu dot org 2010-02-07 4:49 ` hjl at gcc dot gnu dot org [not found] <bug-42512-4@http.gcc.gnu.org/bugzilla/> 2022-10-25 11:40 ` cvs-commit 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=20100108165328.25536.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).