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/44913] [4.6 Regression] -ftree-vectorize causes FAIL: gcc.dg/pr44838.c execution test Date: Sun, 11 Jul 2010 21:58:00 -0000 [thread overview] Message-ID: <20100711215833.3476.qmail@sourceware.org> (raw) In-Reply-To: <bug-44913-14164@http.gcc.gnu.org/bugzilla/> -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Target Milestone|--- |4.6.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44913
next prev parent reply other threads:[~2010-07-11 21:58 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-11 19:40 [Bug tree-optimization/44913] New: " zsojka at seznam dot cz 2010-07-11 21:58 ` rguenth at gcc dot gnu dot org [this message] 2010-07-11 23:11 ` [Bug tree-optimization/44913] " hjl dot tools at gmail dot com 2010-07-23 12:35 ` rguenth at gcc dot gnu dot org 2010-08-23 9:29 ` jakub at gcc dot gnu dot org [not found] <bug-44913-4@http.gcc.gnu.org/bugzilla/> 2010-10-14 10:38 ` rguenth at gcc dot gnu.org 2010-10-14 15:52 ` rguenth at gcc dot gnu.org 2010-10-14 15:55 ` 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=20100711215833.3476.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).