https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104595
--- Comment #10 from Kewen Lin <linkw at gcc dot gnu.org> --- (In reply to rguent...@suse.de from comment #9) > On Wed, 23 Feb 2022, linkw at gcc dot gnu.org wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104595 > > > > --- Comment #8 from Kewen Lin <linkw at gcc dot gnu.org> --- > > I had one local hack and just found it can survive on x86 bootstrapping and > > regression testing. I guess maybe it's good to post here. Just ignore this > > if > > it looks like noise. :) The point is to do the conversion for the loaded > > bool > > value from memory, normally it should be like a nop, but for this test > > case, it > > can help us to generate the expected char comparison. > > Yes, but see my posted patch for a better fix. There's some underlying > missing things we have in bool pattern recog that need to be fixed. > > Treating "external" (that includes memory) bools as 'char' would work > but the type has effect on other IL which causes some ripple down effect > and thus I think doing this isn't going to work in the end. > Got it, thanks for the explanation!
