public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/42431] [4.5 Regression] wrong code for 200.sixtrack with vectorization and -fdata-sections
Date: Fri, 12 Feb 2010 20:36:00 -0000 [thread overview]
Message-ID: <20100212203553.5281.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42431-4503@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from janis at gcc dot gnu dot org 2010-02-12 20:35 -------
Created an attachment (id=19853)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19853&action=view)
minimized executable testcase
Compile with "-m64 -O2 -maltivec -ftree-vectorize -fdata-sections".
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42431
next prev parent reply other threads:[~2010-02-12 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 23:02 [Bug target/42431] New: " janis at gcc dot gnu dot org
2009-12-18 23:04 ` [Bug target/42431] " janis at gcc dot gnu dot org
2009-12-18 23:14 ` [Bug target/42431] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-01-02 16:06 ` rguenth at gcc dot gnu dot org
2010-01-04 18:06 ` janis at gcc dot gnu dot org
2010-02-09 22:38 ` janis at gcc dot gnu dot org
2010-02-12 20:36 ` janis at gcc dot gnu dot org
2010-02-12 20:36 ` janis at gcc dot gnu dot org [this message]
2010-02-12 23:17 ` pthaugen at gcc dot gnu dot org
2010-02-16 20:02 ` bergner at gcc dot gnu dot org
2010-02-17 17:53 ` mmitchel at gcc dot gnu dot org
2010-02-22 12:41 ` rguenth at gcc dot gnu dot org
2010-02-23 21:57 ` [Bug middle-end/42431] " bergner at gcc dot gnu dot org
2010-02-24 21:01 ` meissner at linux dot vnet dot ibm dot com
2010-02-24 22:08 ` bergner at vnet dot ibm dot com
2010-03-04 19:08 ` bergner at gcc dot gnu dot org
2010-03-04 20:00 ` bergner at gcc dot gnu dot org
2010-03-11 20:11 ` meissner 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=20100212203553.5281.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: link
Be 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).