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 target/58158] internal compiler error: in extract_insn, at recog.c:2150 while compiling ImageMagick on mipsel Date: Thu, 22 Aug 2013 21:18:00 -0000 [thread overview] Message-ID: <bug-58158-4-F6Qrw6dX3r@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58158-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58158 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Target|mipsel-linux-gnu |mipsel-linux-gnu | |(loongson2f) --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- This is a loongson2f specific bug in the back-end. It works correctly for -march=octeon/-march=mips32/-march=mips64 .
next prev parent reply other threads:[~2013-08-22 21:18 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-14 16:55 [Bug target/58158] New: " aaro.koskinen at iki dot fi 2013-08-15 6:51 ` [Bug target/58158] " pinskia at gcc dot gnu.org 2013-08-15 17:36 ` aaro.koskinen at iki dot fi 2013-08-16 8:36 ` aaro.koskinen at iki dot fi 2013-08-16 12:39 ` mikpe at it dot uu.se 2013-08-22 21:18 ` pinskia at gcc dot gnu.org [this message] 2013-08-22 21:25 ` pinskia at gcc dot gnu.org 2013-08-22 21:27 ` [Bug target/58158] [4.8/4.9 Regression] ICE with conditional moves on GPRs with a floating point conditional on mipsel with loongson2f pinskia at gcc dot gnu.org 2013-08-24 16:10 ` aaro.koskinen at iki dot fi 2013-10-16 9:51 ` jakub at gcc dot gnu.org 2013-11-21 14:27 ` rguenth at gcc dot gnu.org 2013-12-29 18:32 ` pinskia at gcc dot gnu.org 2013-12-31 1:53 ` biergaizi2009 at gmail dot com 2014-01-01 4:27 ` biergaizi2009 at gmail dot com 2014-02-12 20:23 ` rth at gcc dot gnu.org 2014-02-12 21:45 ` pinskia at gcc dot gnu.org 2014-05-22 9:02 ` [Bug target/58158] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:29 ` [Bug target/58158] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-03-02 23:01 ` sje at gcc dot gnu.org 2015-03-02 23:29 ` aaro.koskinen at iki dot fi 2015-03-03 0:07 ` sje at gcc dot gnu.org 2015-03-06 9:08 ` [Bug target/58158] [4.8/4.9 " biergaizi2009 at gmail dot com 2015-06-23 8:23 ` rguenth at gcc dot gnu.org 2015-06-26 19:59 ` [Bug target/58158] [4.9 " jakub at gcc dot gnu.org 2015-06-26 20:30 ` 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-58158-4-F6Qrw6dX3r@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).