public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46231] gcc.dg/vect/slp-reduc-[36].c FAIL on SPARC Date: Tue, 02 Nov 2010 20:21:00 -0000 [thread overview] Message-ID: <20101102202100.N98HWPrpmwaDQwaxjRXbtMddOHsqFkpbU7jRngTeFDQ@z> (raw) In-Reply-To: <bug-46231-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46231 --- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> 2010-11-02 20:21:44 UTC --- Created attachment 22238 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22238 32-bit -ftree-vectorize -fno-vect-cost-model -mcpu=ultrasparc -mvis -O2 -fdump-tree-vect-details output
next prev parent reply other threads:[~2010-11-02 20:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-29 20:38 [Bug tree-optimization/46231] New: " ro at gcc dot gnu.org 2010-10-29 23:25 ` [Bug tree-optimization/46231] " rguenth at gcc dot gnu.org 2010-11-02 20:21 ` ro at gcc dot gnu.org [this message] 2010-11-02 20:21 ` ro at gcc dot gnu.org 2010-11-02 21:14 ` ebotcazou 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=20101102202100.N98HWPrpmwaDQwaxjRXbtMddOHsqFkpbU7jRngTeFDQ@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).