public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63424] [4.9 regression] Octave -O3 build: internal compiler error: in prepare_cmp_insn, at optabs.c:4237 Date: Thu, 27 Nov 2014 14:30:00 -0000 [thread overview] Message-ID: <bug-63424-4-UOynFl5tTK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63424-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63424 Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2014-11-27 CC| |ramana at gcc dot gnu.org Known to work| |4.8.3 Version|5.0 |4.9.0 Assignee|unassigned at gcc dot gnu.org |renlin.li at arm dot com Target Milestone|--- |4.9.3 Summary|Octave -O3 build: internal |[4.9 regression] Octave -O3 |compiler error: in |build: internal compiler |prepare_cmp_insn, at |error: in prepare_cmp_insn, |optabs.c:4237 |at optabs.c:4237 Ever confirmed|0 |1 Known to fail| |4.9.0, 4.9.1, 4.9.2 --- Comment #5 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- Renlin - can you ask for a 4.9 backport as well. This is a regression from 4.8 in 4.9 now. Fixed on trunk currently.
next prev parent reply other threads:[~2014-11-27 14:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-01 8:43 [Bug c++/63424] New: " david.sherwood at arm dot com 2014-10-21 14:08 ` [Bug target/63424] " renlin.li at arm dot com 2014-10-22 8:58 ` renlin.li at arm dot com 2014-10-28 10:11 ` renlin.li at arm dot com 2014-11-19 16:35 ` renlin at gcc dot gnu.org 2014-11-27 14:30 ` ramana at gcc dot gnu.org [this message] 2015-01-13 16:25 ` [Bug target/63424] [4.9 regression] " renlin at gcc dot gnu.org 2015-01-13 16:32 ` renlin 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-63424-4-UOynFl5tTK@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).