From: Richard Sandiford <richard.sandiford@arm.com>
To: Xi Ruoyao via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
Xi Ruoyao <xry111@mengyan1223.wang>,
Matthew Fortune <mfortune@gmail.com>
Subject: Re: [PATCH] testsuite: mips: use noinline attribute instead of -fno-inline
Date: Fri, 25 Jun 2021 15:40:40 +0100 [thread overview]
Message-ID: <mptfsx680t3.fsf@arm.com> (raw)
In-Reply-To: <c9bb63e1911b04d4d4de7ef3f1f8b11cd1766425.camel@mengyan1223.wang> (Xi Ruoyao via Gcc-patches's message of "Fri, 25 Jun 2021 21:21:17 +0800")
Xi Ruoyao via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> On Fri, 2021-06-25 at 01:02 +0800, Xi Ruoyao wrote:
>> On Thu, 2021-06-24 at 10:48 -0600, Jeff Law wrote:
>> > I'd like to know a bit more here. mips.exp shouldn't care about the
>> > options passed to the compiler and to the best of my knowledge
>> > patch itself is wrong, I question if it's necessary and whether or
>> > not
>> > your just papering over some other issue.
>>
>> There is some logic processing options in mips.exp. Some options are
>> overrided for multilib. It seems the mips.exp was originally designed
>> as:
>>
>> * MIPS options should go in dg-options
>> * Other options should go in dg-additional-options
>>
>> In d2148424165 marxin merged some dg-additional-options into dg-
>> options,
>> exploited the problem.
>>
>> And, the "origin" convention seems already broken: there is something
>> like -funroll-loops which is not a MIPS option, but accepted by
>> mips.exp
>> in dg-options.
>>
>> Possiblities are:
>>
>> (1) this patch
>> (2) make mips.exp accept -fno-inline as "if it is a MIPS option"
>> (3) refactor mips.exp to pass everything itself doesn't know directly
>> to gcc
>
> Attached a diff for mips.exp trying to make it pass everything in dg-
> options which is not known by itself directly to the compiler.
>
> The "smallest fix" is simply adding -fno-inline into mips.exp. However
> I don't like it because I agree with you that mips.exp shouldn't care
> about dg-options, at least don't do it too much.
As I said in the other message, I think the smallest fix is the way to
go though.
Thanks,
Richard
next prev parent reply other threads:[~2021-06-25 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 7:05 Xi Ruoyao
2021-06-24 16:48 ` Jeff Law
2021-06-24 17:02 ` Xi Ruoyao
2021-06-25 11:13 ` Richard Sandiford
2021-06-25 13:21 ` Xi Ruoyao
2021-06-25 14:40 ` Richard Sandiford [this message]
2021-07-08 23:44 ` Jeff Law
2021-07-09 6:42 ` Xi Ruoyao
2021-07-09 11:16 ` Richard Sandiford
2021-07-23 2:21 ` Maciej W. Rozycki
2021-07-23 3:18 ` Xi Ruoyao
2021-07-23 6:01 ` Xi Ruoyao
2021-07-26 13:55 ` Richard Sandiford
2021-07-26 15:02 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mptfsx680t3.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=mfortune@gmail.com \
--cc=xry111@mengyan1223.wang \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).