Hi Segher & Iain! on 2022/9/30 02:37, Segher Boessenkool wrote: > Hi! > > On Thu, Sep 29, 2022 at 07:25:44PM +0100, Iain Sandoe wrote: >>> On 29 Sep 2022, at 18:04, Segher Boessenkool <seg...@kernel.crashing.org> >>> wrote: >>> On Thu, Sep 29, 2022 at 09:16:33AM +0100, Iain Sandoe wrote: >>>> Which means that we do not report an error, but a warning, and then we >>>> force 64b on (taking >>>> the user’s intention to be specified by the explicit ‘-m64’). >>> >>> And that is wrong. Any silent overriding of what the user says is bad. >> >> It is not silent - it warns and then carries on, > > Yes, but I meant the status quo. We agree :-) > >>> Not overriding it (and then later ICEing) is bad as well, so it should >>> be an error here. And in generic code anyway. >> >> As noted, if that change is made we will see what the fallout is :) > > Hopefully it magically makes everything fine ;-)
Okay, if we want to unify the behavior everywhere in generic code, I'll make a separated follow-up patch for it. :) BR, Kewen
