From: Jeff Law <law@redhat.com>
To: David Wohlferd <dw@LimeGreenSocks.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] PR 61692 - Fix for inline asm ICE
Date: Thu, 31 Jul 2014 04:59:00 -0000 [thread overview]
Message-ID: <53D9CCE4.8010305@redhat.com> (raw)
In-Reply-To: <53D6D107.3030404@LimeGreenSocks.com>
On 07/28/14 16:39, David Wohlferd wrote:
>
> On 7/28/2014 12:42 PM, Jeff Law wrote:
>> On 07/27/14 01:26, David Wohlferd wrote:
>>> I'm not sure which maintainer to cc for inline asm stuff?
>>>
>>> I have a release on file with the FSF, but don't have SVN write access.
>>>
>>> Problem:
>>> extract_insn() in recog.c will ICE if (noperands > MAX_RECOG_OPERANDS).
>>> Normally this isn't a problem since expand_asm_operands() in cfgexpand.c
>>> catches and reports a proper error for this condition. However,
>>> expand_asm_operands() only checks (ninputs + noutputs) instead of
>>> (ninputs + noutputs + nlabels), so you can get the ICE when using "asm
>>> goto." See the bugzilla entry for sample code.
>>>
>>> ChangeLog:
>>> 2014-07-27 David Wohlferd <dw@LimeGreenSocks.com>
>>>
>>> PR target/61692
>>> * cfgexpand.c (expand_asm_operands): Count all inline asm
>>> parameters.
>> You should also include 'nclobbers'.
>
> Reading thru asm_noperands (which is what extract_insn uses to count
> operands), I would have thought you were right. But while making this
> fail with nLabels was easy, I wasn't able to get this to ICE at all
> using clobbers (30 labels + 11 clobbers still didn't ICE).
>
> And I'm reluctant to propose that change unless I can see it fail.
I understand, but I'm still quite confident it's the right thing to do.
Running that 30 label + 11 clobber testcase under valgrind might show
the problem, if you can stand waiting that long...
Also, please include the testcase you had nlabels part.
Jeff
next prev parent reply other threads:[~2014-07-31 4:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-27 9:46 David Wohlferd
2014-07-28 20:23 ` Jeff Law
2014-07-28 22:56 ` David Wohlferd
2014-07-31 4:59 ` Jeff Law [this message]
2014-08-01 8:07 ` David Wohlferd
2014-08-01 18:29 ` Jeff Law
2014-09-14 8:13 ` David Wohlferd
2014-09-15 21:51 ` Jeff Law
2014-11-16 5:04 ` David Wohlferd
2014-12-06 12:40 ` David Wohlferd
2014-12-08 21:59 ` Jeff Law
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=53D9CCE4.8010305@redhat.com \
--to=law@redhat.com \
--cc=dw@LimeGreenSocks.com \
--cc=gcc-patches@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: 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).