From: Richard Biener <rguenther@suse.de>
To: Richard Sandiford <richard.sandiford@arm.com>
Cc: Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
"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 14:52:08 +0000 (UTC) [thread overview]
Message-ID: <nycvar.YFH.7.77.849.2301271445350.6551@jbgna.fhfr.qr> (raw)
In-Reply-To: <mpth6wcjh6w.fsf@arm.com>
On Fri, 27 Jan 2023, Richard Sandiford wrote:
> Richard Biener via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> > On Fri, 27 Jan 2023, Kyrylo Tkachov wrote:
> >
> >> 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?
> >
> > Sure, I will add something once the rest of the series is approved.
>
> Mind if I rubber-stamp OK the unreviewed changes? I don't think there's
> a good justification for making a different choice on different targets.
Sure, I've pushed the rest of the changes now. I'm installing below
to changes.html.
Richard.
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html
index 6cd5dd64..9ecd115c 100644
--- a/htdocs/gcc-13/changes.html
+++ b/htdocs/gcc-13/changes.html
@@ -123,6 +123,10 @@ a work-in-progress.</p>
system overcommitting.</li>
</ul>
</li>
+ <li><code>-Ofast</code>, <code>-ffast-math</code> and <code>-funsafe-math-optimizations</code>
+ will no longer add startup code to alter the floating-point environment
+ when producing a shared object with <code>-shared</code>.
+ </li>
</ul>
prev parent reply other threads:[~2023-01-27 14:52 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
2023-01-27 12:24 ` Richard Biener
2023-01-27 12:27 ` Richard Sandiford
2023-01-27 14:52 ` Richard Biener [this message]
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=nycvar.YFH.7.77.849.2301271445350.6551@jbgna.fhfr.qr \
--to=rguenther@suse.de \
--cc=Kyrylo.Tkachov@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=richard.sandiford@arm.com \
--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).