From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Cc: eager@eagercon.com
Subject: Re: [PATCH 3/6] microblaze: Fixes for RTL checking
Date: Tue, 21 Feb 2017 19:28:00 -0000 [thread overview]
Message-ID: <c335afbc-1827-3626-a2f5-73042ba1c89a@redhat.com> (raw)
In-Reply-To: <0b3332af5c3662c0efdf2d930c06457b0fd3cd13.1487685472.git.segher@kernel.crashing.org>
On 02/21/2017 07:48 AM, Segher Boessenkool wrote:
> REGNO can only be called on REGs, not SUBREGs; and INTVAL does not work
> on REGs.
>
> 2017-02-21 Segher Boessenkool <segher@kernel.crashing.org>
>
> * config/microblaze/microblaze.c (microblaze_expand_shift): Do not
> test for register moves to themselves.
> * config/microblaze/microblaze.md (*ashlsi3_byone, *ashrsi3_byone,
> *lshrsi3_byone): Test for const1_rtx instead of calling INTVAL on
> something that isn't necessarily a CONST_INT.
So I wanted to make sure that the avoidance of a nop-move resulting from
a nop-shift wasn't because the ISA couldn't encode a nop-move (and yes,
I've run into such ISAs).
The microblaze doesn't seem to have any trouble encoding a nop move, so
if we were to generate one due to this change it won't cause a problem.
OK for the trunk.
Jeff
next prev parent reply other threads:[~2017-02-21 19:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 14:48 [PATCH 0/6] Fallout from " Segher Boessenkool
2017-02-21 14:48 ` [PATCH 2/6] cris: Fix for " Segher Boessenkool
2017-02-21 15:03 ` Hans-Peter Nilsson
2017-02-21 14:49 ` [PATCH 1/6] c6x: " Segher Boessenkool
2017-02-21 15:09 ` Bernd Schmidt
2017-02-21 14:49 ` [PATCH 4/6] nios2: Fixes " Segher Boessenkool
2017-02-21 19:33 ` Jeff Law
2017-02-21 19:53 ` Sandra Loosemore
2017-02-24 22:45 ` Sandra Loosemore
2017-02-21 14:49 ` [PATCH 6/6] sh: " Segher Boessenkool
2017-02-21 15:49 ` Oleg Endo
2017-02-21 16:32 ` Segher Boessenkool
2017-02-21 14:49 ` [PATCH 3/6] microblaze: " Segher Boessenkool
2017-02-21 19:28 ` Jeff Law [this message]
2017-02-21 20:11 ` Michael Eager
2017-02-21 20:33 ` Segher Boessenkool
2017-02-21 21:07 ` Michael Eager
2017-02-24 23:12 ` Segher Boessenkool
2017-02-21 20:19 ` Jakub Jelinek
2017-02-21 20:37 ` Michael Eager
2017-02-21 20:41 ` Jakub Jelinek
2017-02-21 21:23 ` Segher Boessenkool
2017-02-21 15:01 ` [PATCH 5/6] pa: " Segher Boessenkool
2017-02-21 19:12 ` Jeff Law
2017-02-21 15:16 ` [PATCH] arc: " Segher Boessenkool
2017-02-21 19:27 ` Jeff Law
2017-02-24 19:20 ` Claudiu Zissulescu
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=c335afbc-1827-3626-a2f5-73042ba1c89a@redhat.com \
--to=law@redhat.com \
--cc=eager@eagercon.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).