Re: Executor code - found an instance of a WHILE that should just be an IF
On Fri, May 14, 2021 at 10:27 AM David Rowley wrote: > > Thanks for the votes. Pushed. Thanks! Regards, Greg Nancarrow Fujitsu Australia
Re: Executor code - found an instance of a WHILE that should just be an IF
On Fri, 14 May 2021 at 00:27, Julien Rouhaud wrote: > > On Thu, May 13, 2021 at 08:06:18PM +0900, Michael Paquier wrote: > > On Thu, May 13, 2021 at 08:20:36PM +1200, David Rowley wrote: > > > Since there's no bug fix here, I thought that there's not much point > > > in backpatching this. > > > > Indeed. I would not bother with a back-patch either. > > > > > Does anyone object to making this small change in master? > > > > No objections from here. > > +1 to both. Thanks for the votes. Pushed. David
Re: Executor code - found an instance of a WHILE that should just be an IF
On Thu, May 13, 2021 at 08:06:18PM +0900, Michael Paquier wrote: > On Thu, May 13, 2021 at 08:20:36PM +1200, David Rowley wrote: > > Since there's no bug fix here, I thought that there's not much point > > in backpatching this. > > Indeed. I would not bother with a back-patch either. > > > Does anyone object to making this small change in master? > > No objections from here. +1 to both.
Re: Executor code - found an instance of a WHILE that should just be an IF
On Thu, May 13, 2021 at 08:20:36PM +1200, David Rowley wrote: > Since there's no bug fix here, I thought that there's not much point > in backpatching this. Indeed. I would not bother with a back-patch either. > Does anyone object to making this small change in master? No objections from here. -- Michael signature.asc Description: PGP signature
Re: Executor code - found an instance of a WHILE that should just be an IF
On Mon, 10 May 2021 at 23:49, David Rowley wrote: > > On Mon, 10 May 2021 at 21:16, Greg Nancarrow wrote: > > During debugging I noticed some code in ExecResult() where a WHILE > > loop is being used with an unconditional RETURN at the end of the > > block (which is intentional, looking at the history of changes), but > > now there's no actual use of the loop in any way. The code should > > probably be changed to just use IF for clarity. > > I've attached a patch. > > Looks like leftovers from ea15e1867. > > I don't think this will affect any code generation but you are right, > it should be an "if". Since there's no bug fix here, I thought that there's not much point in backpatching this. Does anyone object to making this small change in master? David
Re: Executor code - found an instance of a WHILE that should just be an IF
On Mon, 10 May 2021 at 21:16, Greg Nancarrow wrote: > During debugging I noticed some code in ExecResult() where a WHILE > loop is being used with an unconditional RETURN at the end of the > block (which is intentional, looking at the history of changes), but > now there's no actual use of the loop in any way. The code should > probably be changed to just use IF for clarity. > I've attached a patch. Looks like leftovers from ea15e1867. I don't think this will affect any code generation but you are right, it should be an "if". David
Executor code - found an instance of a WHILE that should just be an IF
Hi, During debugging I noticed some code in ExecResult() where a WHILE loop is being used with an unconditional RETURN at the end of the block (which is intentional, looking at the history of changes), but now there's no actual use of the loop in any way. The code should probably be changed to just use IF for clarity. I've attached a patch. Regards, Greg Nancarrow Fujitsu Australia v1-0001-Change-an-instance-of-WHILE-to-IF-in-executor-code.patch Description: Binary data
