public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46184] [4.6 Regression] ICE: SIGSEGV in vectorizable_reduction (tree-vect-loop.c:4067) with -O -ftree-vectorize -fno-tree-copy-prop -fno-tree-dce Date: Tue, 26 Oct 2010 14:15:00 -0000 [thread overview] Message-ID: <20101026141500.rjvD_a4QbfEnPOmeDnvRbxw8idHQRd2F3qvFpBpvPBQ@z> (raw) In-Reply-To: <bug-46184-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46184 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.6.0
next prev parent reply other threads:[~2010-10-26 14:15 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-26 13:57 [Bug tree-optimization/46184] New: " zsojka at seznam dot cz 2010-10-26 14:15 ` rguenth at gcc dot gnu.org [this message] 2010-10-26 16:32 ` [Bug tree-optimization/46184] " hjl.tools at gmail dot com 2010-10-29 12:53 ` rguenth at gcc dot gnu.org 2010-11-02 14:24 ` rguenth at gcc dot gnu.org 2010-11-02 15:46 ` rguenth at gcc dot gnu.org 2010-11-02 15:48 ` 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=20101026141500.rjvD_a4QbfEnPOmeDnvRbxw8idHQRd2F3qvFpBpvPBQ@z \ --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).