From: Florian Weimer <fweimer@redhat.com>
To: Andrew Pinski via Gcc <gcc@gcc.gnu.org>
Cc: Andrew Pinski <pinskia@gmail.com>
Subject: Re: Deprecating -fgnu-tm support for GCC 14 and removing it for GCC 15
Date: Sun, 17 Dec 2023 17:26:34 +0100 [thread overview]
Message-ID: <87wmtc4wxx.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CA+=Sn1kRnWrw+4WMt9u4m5Cp7GzqAtfcwegUyntic-FWf87Fvw@mail.gmail.com> (Andrew Pinski via Gcc's message of "Sat, 16 Dec 2023 12:15:42 -0800")
* Andrew Pinski via Gcc:
> -fgnu-tm support has not been improved since GCC 5 or earlier. It is
> not even supported with LTO. Does it make sense to deprecate the
> support for GCC 14 and remove it in GCC 15?
Is this the stuff around libitm and that adds _ITM_registerTMCloneTable
and _ITM_deregisterTMCloneTable symbol references to *all* binaries
(whether they use transactional memory or not)?
Thanks,
Florian
next prev parent reply other threads:[~2023-12-17 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 20:15 Andrew Pinski
2023-12-17 16:26 ` Florian Weimer [this message]
2023-12-17 18:05 ` Andrew Pinski
2023-12-17 21:20 ` Eric Gallager
2023-12-18 1:33 ` Andrew Pinski
2023-12-18 8:01 ` Richard Biener
2023-12-20 16:40 ` Jason Merrill
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=87wmtc4wxx.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@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).