From: Chenghua Xu <xuchenghua@loongson.cn>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 5/9] loongarch: Don't add crtfastmath.o for -shared
Date: Fri, 27 Jan 2023 11:34:48 +0800 [thread overview]
Message-ID: <b02fc5a2-da50-e9f1-a24d-b3c28f4b3daf@loongson.cn> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2301230859500.6551@jbgna.fhfr.qr>
Sorry for delay. Pushed as r13-5424 with s/loongarch/LoongArch/ in
commit message.
Thanks for fix this.
在 2023/1/23 下午4:59, Richard Biener 写道:
> On Fri, 13 Jan 2023, Richard Biener wrote:
>
>> Don't add crtfastmath.o for -shared to avoid altering the FP
>> environment when loading a shared library.
> Ping.
>
>> PR target/55522
>> * config/loongarch/gnu-user.h (GNU_USER_TARGET_MATHFILE_SPEC):
>> Don't add crtfastmath.o for -shared.
>> ---
>> gcc/config/loongarch/gnu-user.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gcc/config/loongarch/gnu-user.h b/gcc/config/loongarch/gnu-user.h
>> index c5b1afe530d..1dc6add62d4 100644
>> --- a/gcc/config/loongarch/gnu-user.h
>> +++ b/gcc/config/loongarch/gnu-user.h
>> @@ -49,7 +49,7 @@ along with GCC; see the file COPYING3. If not see
>> /* Similar to standard Linux, but adding -ffast-math support. */
>> #undef GNU_USER_TARGET_MATHFILE_SPEC
>> #define GNU_USER_TARGET_MATHFILE_SPEC \
>> - "%{Ofast|ffast-math|funsafe-math-optimizations:crtfastmath.o%s}"
>> + "%{Ofast|ffast-math|funsafe-math-optimizations:%{!shared:crtfastmath.o%s}}"
>>
>> #undef LIB_SPEC
>> #define LIB_SPEC GNU_USER_TARGET_LIB_SPEC
>>
next prev parent reply other threads:[~2023-01-27 3:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 8:59 Richard Biener
2023-01-27 3:34 ` Chenghua Xu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 8:01 Richard Biener
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=b02fc5a2-da50-e9f1-a24d-b3c28f4b3daf@loongson.cn \
--to=xuchenghua@loongson.cn \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).