This is the mail archive of the
mailing list for the GCC project.
Re: movstrictqi/movstricthi fix for h8300
- To: bernds at redhat dot co dot uk
- Subject: Re: movstrictqi/movstricthi fix for h8300
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Tue, 12 Sep 2000 07:19:49 -0700
- Cc: law at cygnus dot com, hiller at cygnus dot com, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Organization: CodeSourcery, LLC
- References: <23866.968709296@upchuck><Pine.LNX.firstname.lastname@example.org>
>>>>> "Bernd" == Bernd Schmidt <email@example.com> writes:
Bernd> I think it would be cleaner to represent a movstrict
Bernd> pattern as something like
Bernd> (set (reg X) (ior (and X 0xFF....00) (zero_extend Y)))
Bernd> This might even help the combiner, who knows.
I couldn't agree more, both with the overall sentiment you express,
and also with this particular case. If you can figure out how to get
rid of this, go for it. If that causes slightly worse code
generation, so be it: the win will still be worth it in the long run.
It should be relatively simple to show the insn recognizers how to
take the pattern you show above and do the right thing.
Mark Mitchell firstname.lastname@example.org
CodeSourcery, LLC http://www.codesourcery.com