public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50928] m32c ICE building RTEMS Date: Wed, 21 Jan 2015 03:34:00 -0000 [thread overview] Message-ID: <bug-50928-4-iKfjQH24gv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50928-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50928 --- Comment #13 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- ok, now I see. the binutils-2.25.tar.gz works, but if we build directly from the git it does not. is this a new check that makes this problem? regarding my patch on pr26255.c, this happens: m32c-elf-gcc -O1 -mcpu=m32c pr26255.c pr26255.c: In function 'foo': pr26255.c:31:1: error: insn does not satisfy its constraints: } ^ (insn 62 61 63 2 (set (reg:PSI 4 a0) (plus:PSI (reg:PSI 4 a0) (reg/v/f:PSI 28 [ w ]))) pr26255.c:29 5 {addpsi3} (expr_list:REG_EQUIV (plus:PSI (reg/v/f:PSI 28 [ w ]) (const_int 128 [0x80])) (nil))) pr26255.c:31:1: internal compiler error: in extract_constrain_insn, at recog.c:2246 0x9e9478 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) ../../gcc-trunk/gcc/rtl-error.c:110 0x9e949f _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) ../../gcc-trunk/gcc/rtl-error.c:121 0x9c0505 extract_constrain_insn(rtx_insn*) ../../gcc-trunk/gcc/recog.c:2246 0x9a1a5d reload_cse_simplify_operands ../../gcc-trunk/gcc/postreload.c:430 0x9a4485 reload_cse_simplify ../../gcc-trunk/gcc/postreload.c:207 0x9a4485 reload_cse_regs_1 ../../gcc-trunk/gcc/postreload.c:246 0x9a459b reload_cse_regs ../../gcc-trunk/gcc/postreload.c:94 0x9a459b execute ../../gcc-trunk/gcc/postreload.c:2367 I had similar traps and could avoid them by adding an explicit mode to some patterns. But here I have no idea at the moment. DJ do you see anything obvious in the addpsi3 pattern?
next prev parent reply other threads:[~2015-01-21 3:34 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-30 21:08 [Bug c/50928] New: " joel at gcc dot gnu.org 2011-10-30 21:10 ` [Bug c/50928] " joel at gcc dot gnu.org 2012-11-03 17:22 ` [Bug c/50928] m32c " joel at gcc dot gnu.org 2012-11-03 17:23 ` joel at gcc dot gnu.org 2013-03-26 8:30 ` corsepiu at gcc dot gnu.org 2015-01-15 18:14 ` [Bug target/50928] " joel at gcc dot gnu.org 2015-01-20 0:54 ` dj at redhat dot com 2015-01-20 18:41 ` joel at gcc dot gnu.org 2015-01-20 20:01 ` bernd.edlinger at hotmail dot de 2015-01-20 20:08 ` dj at redhat dot com 2015-01-20 21:36 ` dj at redhat dot com 2015-01-21 3:34 ` bernd.edlinger at hotmail dot de [this message] 2015-01-23 16:34 ` edlinger at gcc dot gnu.org 2015-01-24 2:39 ` dj at redhat dot com
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-50928-4-iKfjQH24gv@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).