(In reply to matoro from comment #9)
> (In reply to Uroš Bizjak from comment #8)
> > Created attachment 55504 [details]
> > Proposed patch.
> >
> > Can someone please bootstrap and test the attached patch?
>
> I can queue this up to test on real hardware. By bootstrap, do you mean
> with --enable-bootstrap, and by test do you mean a full testsuite run or
> just checking that it doesn't ICE on the reproducer here?
I have already checked that it doesn't ICE with a crosscompiler. Regarding the bootstrap, please note that --enable-bootstrap is the default nowadays, so the option it is not needed to make a full build ("bootstrap"). Also, "make -j N -k check-gcc" should be enough to test the compiler, since other parts of the compiler never exercise -mbuild-constants (N in the command should be substituted with a number of processors to parallelize the testsuite run).
(In reply to matoro from comment #9)
> (In reply to Uroš Bizjak from comment #8)
> > Created attachment 55504 [details]
> > Proposed patch.
> >
> > Can someone please bootstrap and test the attached patch?
>
> I can queue this up to test on real hardware. By bootstrap, do you mean
> with --enable-bootstrap, and by test do you mean a full testsuite run or
> just checking that it doesn't ICE on the reproducer here?
I have already checked that it doesn't ICE with a crosscompiler. Regarding the bootstrap, please note that --enable-bootstrap is the default nowadays, so the option it is not needed to make a full build ("bootstrap"). Also, "make -j N -k check-gcc" should be enough to test the compiler, since other parts of the compiler never exercise -mbuild-constants (N in the command should be substituted with a number of processors to parallelize the testsuite run).