This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: doloop insn generated incorrectly (wrong mode)

From: Paul Koning <paulkoning at comcast dot net>
To: Segher Boessenkool <segher at kernel dot crashing dot org>
Cc: GCC Development <gcc at gcc dot gnu dot org>
Date: Thu, 11 Oct 2018 08:51:15 -0400
Subject: Re: doloop insn generated incorrectly (wrong mode)
References: <46986208-BB49-4386-9BBE-7EEF1C653686@comcast.net> <20181011071144.GG29268@gate.crashing.org>


> 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

References:
- doloop insn generated incorrectly (wrong mode)
  - From: Paul Koning
- Re: doloop insn generated incorrectly (wrong mode)
  - From: Segher Boessenkool

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]