Re: Deprecating -fgnu-tm support for GCC 14 and removing it for GCC 15

2023-12-17 Thread Florian Weimer via Gcc 
* 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

Re: Deprecating -fgnu-tm support for GCC 14 and removing it for GCC 15

2023-12-17 Thread Andrew Pinski via Gcc 
On Sun, Dec 17, 2023 at 8:26 AM Florian Weimer  wrote:
>
> * 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)?

Yes. and the front-end support for it.

Thanks,
Andrew

>
> Thanks,
> Florian
>

Re: Deprecating -fgnu-tm support for GCC 14 and removing it for GCC 15

2023-12-17 Thread Eric Gallager 
On Sat, Dec 16, 2023 at 3:16 PM Andrew Pinski via Gcc  wrote:
>
> -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?
>
> Thanks,
> Andrew Pinski

Personally, since GCC is in stage 3 now, I would push that schedule
back a release and move deprecation to GCC 15, and then only remove it
for GCC 16 if no one objects, but then again I don't actually use
-fgnu-tm myself, so I wouldn't be too upset if the faster schedule is
chosen instead.
Eric Gallager

gcc-14-20231217 is now available

2023-12-17 Thread GCC Administrator via Gcc 
Snapshot gcc-14-20231217 is now available on
  https://gcc.gnu.org/pub/gcc/snapshots/14-20231217/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch master 
revision 5060825aa78b3da036df6437390fd42d094d8f15

You'll find:

 gcc-14-20231217.tar.xz   Complete GCC

  SHA256=1545b59c5573694616f5bcf218d708096c35c1b4971e19cab135a167b0bebfe8
  SHA1=3da6e2ae6b13690ffca6e394d208c3c3700b970c

Diffs from 14-20231210 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-14
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

Re: Deprecating -fgnu-tm support for GCC 14 and removing it for GCC 15

2023-12-17 Thread Andrew Pinski via Gcc 
On Sun, Dec 17, 2023 at 1:20 PM Eric Gallager  wrote:
>
> On Sat, Dec 16, 2023 at 3:16 PM Andrew Pinski via Gcc  wrote:
> >
> > -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?
> >
> > Thanks,
> > Andrew Pinski
>
> Personally, since GCC is in stage 3 now, I would push that schedule
> back a release and move deprecation to GCC 15, and then only remove it
> for GCC 16 if no one objects, but then again I don't actually use
> -fgnu-tm myself, so I wouldn't be too upset if the faster schedule is
> chosen instead.

Considering -fgnu-tm has been broken for LTO ever since LTO was
introduced, and broken with -fsanitize=undefined and broken with many
code that might use internal functions (known since 2015), I suspect
nobody is using this option in production nor even trying it out. If
this was stage1, I might even just recommend removing the support. But
deprecating it during stage 3 seems like a fair compromise.

> Eric Gallager