This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] MIPS: Fix GCC `noreorder' for undefined R5900 short loops
- From: Jeff Law <law at redhat dot com>
- To: "Maciej W. Rozycki" <macro at linux-mips dot org>, Fredrik Noring <noring at nocrew dot org>
- Cc: Paul Burton <paul dot burton at mips dot com>, Matthew Fortune <mfortune at gmail dot com>, Jürgen Urban <JuergenUrban at gmx dot de>, gcc-patches at gcc dot gnu dot org
- Date: Mon, 22 Jul 2019 16:15:03 -0600
- Subject: Re: [PATCH] MIPS: Fix GCC `noreorder' for undefined R5900 short loops
- References: <20190721171726.GA47580@sx9> <alpine.LFD.firstname.lastname@example.org> <20190722155506.GA2726@sx9> <alpine.LFD.email@example.com>
On 7/22/19 3:47 PM, Maciej W. Rozycki wrote:
> Hi Fredrik,
>> I'm glad to hear from you again!
> I'm not dead, just distracted.
>>> I think that should be a GAS warning really (similarly to macros that
>>> expand to multiple instructions in a delay slot) as people ought to be
>>> allowed to do what they wish, and then `-Werror' can be used for code
>>> quality enforcement (and possibly disabled on a case-by-case basis).
>> How can one reasonably prevent the bug when compiling a whole Linux
>> distribution with thousands of packages if GAS merely warns and proceeds
>> in many cases?
> I think the tools must not set a policy. By using `.set noreorder' the
> user told the toolchain he knows better and asked to keep its hands away.