From: Georg-Johann Lay <avr@gjlay.de>
To: Denis Chertykov <chertykov@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>, Jeff Law <law@redhat.com>
Subject: Re: [patch,avr,4.9] Fix PR63633 ICEs for expanders colliding hard-regs
Date: Thu, 30 Oct 2014 11:05:00 -0000 [thread overview]
Message-ID: <545215D6.9070202@gjlay.de> (raw)
In-Reply-To: <CADOs=zYjfe5FvXiLTiDPb1EUtHko8GyP9qPekmTLDMK7-svw=Q@mail.gmail.com>
Am 10/30/2014 07:48 AM, schrieb Denis Chertykov:
>> Am 10/28/2014 01:34 PM, schrieb Georg-Johann Lay:
>>>
>>> Middle-end might come up with hard registers as operands for expanders
>>> which
>>> clobber respective hard regs. This patch uses freshly created pseudos for
>>> respective expander operands and emits pseudo <-> hard move insn.
>>>
>>> Ok for 4.9.2?
>>
>
> Ok.
> Please apply.
>
> Denis.
I am also waiting for approval from release manager.
Johann
next prev parent reply other threads:[~2014-10-30 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 12:34 Georg-Johann Lay
2014-10-28 12:55 ` Georg-Johann Lay
2014-10-30 7:25 ` Denis Chertykov
2014-10-30 11:05 ` Georg-Johann Lay [this message]
2014-10-30 11:11 ` Jakub Jelinek
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=545215D6.9070202@gjlay.de \
--to=avr@gjlay.de \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).