From: Trevor Saunders <tbsaunde@tbsaunde.org>
To: Bernd Schmidt <bschmidt@redhat.com>
Cc: tbsaunde+gcc@tbsaunde.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] pr 65702 - error out for invalid register asms earlier
Date: Mon, 25 Jan 2016 15:55:00 -0000 [thread overview]
Message-ID: <20160125155406.GA14223@tsaunders-iceball.corp.tor1.mozilla.com> (raw)
In-Reply-To: <56A64282.6050504@redhat.com>
On Mon, Jan 25, 2016 at 04:42:58PM +0100, Bernd Schmidt wrote:
> On 01/25/2016 04:36 PM, tbsaunde+gcc@tbsaunde.org wrote:
> >$subject. To avoid regressions I kept the checks when generating rtl, but I
> >believe its impossible for those to trigger now and we can remove the checks.
> >
> >bootstrapped + regtested on x86_64-linux-gnu, ok?
>
> Is this still an issue? I committed a fix for a similar PR a few weeks ago,
> and I can't make the testcase from 65702 ICE.
hrm, I guess my tree was more out of date than I thought, it doesn't
ICE for me at r232662.
Never mind then ;)
Trev
>
>
> Bernd
prev parent reply other threads:[~2016-01-25 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 15:37 tbsaunde+gcc
2016-01-25 15:43 ` Bernd Schmidt
2016-01-25 15:55 ` Trevor Saunders [this message]
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=20160125155406.GA14223@tsaunders-iceball.corp.tor1.mozilla.com \
--to=tbsaunde@tbsaunde.org \
--cc=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=tbsaunde+gcc@tbsaunde.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).