public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/46149] New: [4.6 Regression] 26_numerics/valarray/27867.cc FAILs with -O2 -fno-tree-sra Date: Sat, 23 Oct 2010 14:54:00 -0000 [thread overview] Message-ID: <bug-46149-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46149 Summary: [4.6 Regression] 26_numerics/valarray/27867.cc FAILs with -O2 -fno-tree-sra Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 22133 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22133 packed preprocessed source Output: $ g++ -O2 -fno-tree-sra 27867.ii -std=c++0x $ ./a.out Segmentation fault Tested revisions: r165822 - fail r163636 - fail r161659 - fail r159696 - OK 4.5 r165781 - OK
next reply other threads:[~2010-10-23 14:54 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-23 14:54 zsojka at seznam dot cz [this message] 2010-10-23 14:57 ` [Bug tree-optimization/46149] " zsojka at seznam dot cz 2010-10-23 17:20 ` hjl.tools at gmail dot com 2010-10-26 14:14 ` rguenth at gcc dot gnu.org 2010-11-02 13:25 ` rguenth at gcc dot gnu.org 2010-11-02 17:00 ` rguenth at gcc dot gnu.org 2010-11-02 17:01 ` 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=bug-46149-4@http.gcc.gnu.org/bugzilla/ \ --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).