From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Richard Biener <rguenther@suse.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "hongtao.liu@intel.com" <hongtao.liu@intel.com>,
"ubizjak@gmail.com" <ubizjak@gmail.com>
Subject: RE: [PATCH 0/9] Don't add crtfastmath.o for -shared
Date: Fri, 27 Jan 2023 12:17:12 +0000 [thread overview]
Message-ID: <PAXPR08MB6926CE98D9773429BDA62BC293CC9@PAXPR08MB6926.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <51no4077-nrro-q647-4q33-on5s277on191@fhfr.qr>
Thanks for fixing this Richard.
> -----Original Message-----
> From: Gcc-patches <gcc-patches-
> bounces+kyrylo.tkachov=arm.com@gcc.gnu.org> On Behalf Of Richard
> Biener via Gcc-patches
> Sent: Friday, January 13, 2023 8:05 AM
> To: gcc-patches@gcc.gnu.org
> Cc: hongtao.liu@intel.com; ubizjak@gmail.com
> Subject: [PATCH 0/9] Don't add crtfastmath.o for -shared
>
>
> This is a series completing the fix for PR55522 which got a fix for
> x86-linux already but left all other targets unfixed (including
> x86-cygwin, x86-darwin and x86-mingw32). The following series
> applies a similar change to other specs using crtfastmath.o,
> the changes are untested.
>
> Target maintainers are CCed and I hope they can smoke-test the
> changes.
>
Do you think it's something we should mention in changes.html for GCC 13?
Kyrill
> x86 maintainers, can you please adjust the missed specs yourself?
>
> Thanks,
> Richard.
next prev parent reply other threads:[~2023-01-27 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 8:05 Richard Biener
2023-01-13 8:08 ` Hongtao Liu
2023-01-27 12:17 ` Kyrylo Tkachov [this message]
2023-01-27 12:24 ` Richard Biener
2023-01-27 12:27 ` Richard Sandiford
2023-01-27 14:52 ` 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=PAXPR08MB6926CE98D9773429BDA62BC293CC9@PAXPR08MB6926.eurprd08.prod.outlook.com \
--to=kyrylo.tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=rguenther@suse.de \
--cc=ubizjak@gmail.com \
/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).