public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54741] GCC 4.4, 4.5, 4.6 4.7 (probably 4.8) Generates un-usable code on AVX supported CPUs (FreeBSD) Date: Sat, 29 Sep 2012 01:08:00 -0000 [thread overview] Message-ID: <bug-54741-4-x3JRjgm4GZ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54741-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54741 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2012-09-29 Ever Confirmed|0 |1 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-09-29 01:07:54 UTC --- What is the instruction it is causing an illegal instruction signal? Run the resulting program using gdb to find out.
next prev parent reply other threads:[~2012-09-29 1:08 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-29 0:45 [Bug c++/54741] New: " ace.of.zerosync at gmail dot com 2012-09-29 1:08 ` pinskia at gcc dot gnu.org [this message] 2012-09-29 5:43 ` [Bug c++/54741] " ace.of.zerosync at gmail dot com 2012-10-01 10:20 ` rguenth at gcc dot gnu.org 2012-10-01 11:20 ` mikpe at it dot uu.se 2012-10-01 12:55 ` [Bug target/54741] " hjl.tools at gmail dot com 2012-10-01 13:27 ` jakub at gcc dot gnu.org 2012-10-01 13:33 ` hjl.tools at gmail dot com 2012-10-02 7:15 ` ace.of.zerosync at gmail dot com 2012-10-02 7:18 ` ace.of.zerosync at gmail dot com 2012-10-02 9:59 ` ubizjak at gmail dot com 2012-10-02 16:59 ` ace.of.zerosync at gmail dot com 2012-10-02 17:00 ` ace.of.zerosync at gmail dot com 2012-10-02 19:49 ` hjl at gcc dot gnu.org 2012-10-02 20:25 ` hjl at gcc dot gnu.org 2012-10-02 20:31 ` hjl at gcc dot gnu.org 2012-10-02 20:32 ` hjl.tools at gmail dot com 2012-10-03 17:33 ` andrew.w.nosenko at gmail dot com 2012-10-03 17:36 ` andrew.w.nosenko at gmail dot com 2012-10-03 18:06 ` jakub at gcc dot gnu.org 2012-10-03 18:48 ` jakub 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-54741-4-x3JRjgm4GZ@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).