doloop insn generated incorrectly (wrong mode)
Paul Koning
paulkoning@comcast.net
Thu Oct 11 12:51:00 GMT 2018
> On Oct 11, 2018, at 3:11 AM, Segher Boessenkool <segher@kernel.crashing.org> wrote:
>
> Hi!
>
> On Wed, Oct 10, 2018 at 08:55:12PM -0400, Paul Koning wrote:
>
> [ snip ]
>
>> ...
>> Why is this happening, and how can I fix it (short of removing the doloop_end pattern)? I see a comment in loop-doloop.c about handling a FAIL of the pattern -- am I going to have to check that the wrong mode is being passed in and FAIL if so?
>
> That is exactly what other targets do. Maybe you can improve doloop so
> this isn't necessary anymore? :-)
Maybe. For now I'll take the expand and check approach. And propose a doc patch to explain that this is needed, because it's an unusual situation.
paul
More information about the Gcc
mailing list