From: Andreas Schwab <schwab@linux-m68k.org>
To: Kelvin Nilsen <kdnilsen@linux.vnet.ibm.com>
Cc: gcc-patches@gcc.gnu.org, bschmidt@redhat.com, law@redhat.com
Subject: Re: [PATCH v4] PR48344: Fix unrecognizable insn error with -fstack-limit-register=r2
Date: Fri, 30 Sep 2016 20:11:00 -0000 [thread overview]
Message-ID: <87shsh88c6.fsf@linux-m68k.org> (raw)
In-Reply-To: <56BCA4E4.6030100@linux.vnet.ibm.com> (Kelvin Nilsen's message of "Thu, 11 Feb 2016 08:12:36 -0700")
On Feb 11 2016, Kelvin Nilsen <kdnilsen@linux.vnet.ibm.com> wrote:
> * opts-global.c (handle_common_deferred_options): Introduce and
> initialize two global variables to remember command-line options
> specifying a stack-limiting register.
> * opts.h: Add extern declarations of the two new global variables.
> * emit-rtl.c (init_emit_once): Initialize the stack_limit_rtx
> variable based on the values of the two new global variables.
That breaks gcc.target/m68k/stack-limit-1.c:
/daten/aranym/gcc/test/gcc/testsuite/gcc.target/m68k/stack-limit-1.c: In function 'dummy':
/daten/aranym/gcc/test/gcc/testsuite/gcc.target/m68k/stack-limit-1.c:6:1: error: unrecognizable insn:
(insn 10 9 11 (trap_if (ltu (cc0)
(const_int 0 [0]))
(const_int 1 [0x1])) /daten/aranym/gcc/test/gcc/testsuite/gcc.target/m68k/stack-limit-1.c:6 -1
(nil))
/daten/aranym/gcc/test/gcc/testsuite/gcc.target/m68k/stack-limit-1.c:6:1: internal compiler error: in extract_insn, at recog.c:2287
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2016-09-30 20:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 15:12 Kelvin Nilsen
2016-02-11 15:42 ` Bernd Schmidt
2016-09-30 20:11 ` Andreas Schwab [this message]
2016-10-13 10:58 ` Bernd Schmidt
2016-10-13 20:23 ` Andreas Schwab
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=87shsh88c6.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kdnilsen@linux.vnet.ibm.com \
--cc=law@redhat.com \
/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: link
Be 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).