From Newsgroup: comp.lang.ada

Keith Thompson <[email protected]> writes:

Simon Wright <[email protected]> writes:

Björn Persson <Bjorn@rombobjörn.se> writes:

It happened today in GCC 14.2.1 (as packaged in Fedora 41), so no, not
only in 14.2.0.

There's no official FSF 14.2.1 release - it may just be like Alire,
which only handles 3 levels, so they call the first packaging of 14.2.0
14.2.1. If you say 'gcc -v' it'll probably say 14.2.0.

Of course I could be completely wrong and Fedora have added lots of
value!

I see some potential for confusion, since there almost certainly will be
an official gcc 14.2.1 release in the near future. That official
release will include code that's not included in what Fedora calls gcc 14.2.1. It's a point release, so I wouldn't expect substantial changes,
but still, I think Fedora should use a different naming scheme.

I have this vague memory that 14.2.1 is a draft for 14.3.0, and that GCC
never has .1 _releases_. In the same way that 15.0.0 migrates to 15.0.1
before the 15.1.0 release.

Yes, see [1], section "Version Numbering Scheme for GCC 5 and Up".

Also, in gcc-mirror on github, gcc/BASE-VER in the releases/gcc-14
branch [2] holds 14.2.1.

[1] https://gcc.gnu.org/develop.html
[2] https://github.com/gcc-mirror/gcc/blob/releases/gcc-14/gcc/BASE-VER
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.lang.ada

Keith Thompson wrote:

Simon Wright <[email protected]> writes:

Björn Persson <Bjorn@rombobjörn.se> writes:

It happened today in GCC 14.2.1 (as packaged in Fedora 41), so no, not
only in 14.2.0.

There's no official FSF 14.2.1 release - it may just be like Alire,
which only handles 3 levels, so they call the first packaging of 14.2.0 14.2.1. If you say 'gcc -v' it'll probably say 14.2.0.

$ LANG=en gcc -v
Using built-in specs.
COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/14/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap --enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,m2,lto --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared --enable-threads=posix --enable-checking=release --enable-multilib --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --with-gcc-major-version-only --enable-libstdcxx-backtrace --with-libstdcxx-zoneinfo=/usr/share/zoneinfo --with-linker-hash-style=gnu --enable-plugin --enable-initfini-array --with-isl=/builddir/build/BUILD/gcc-14.2.1-build/gcc-14.2.1-20240912/obj-x86_64-redhat-linux/isl-install --enable-offload-targets=nvptx-none,amdgcn-amdhsa --enable-offload-defaulted --without-cuda-driver --enable-gnu-indirect-function --enable-cet --with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux --with-build-config=bootstrap-lto --enable-link-serialization=1
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.2.1 20240912 (Red Hat 14.2.1-3) (GCC)

I see some potential for confusion, since there almost certainly will be
an official gcc 14.2.1 release in the near future. That official
release will include code that's not included in what Fedora calls gcc 14.2.1. It's a point release, so I wouldn't expect substantial changes,
but still, I think Fedora should use a different naming scheme.

Anyone who needs to know the exact state of the code packaged in Fedora
41 can find the Git revision and all the patches here: https://src.fedoraproject.org/rpms/gcc/blob/f41/f/gcc.spec
If someone has a problem with the version numbering, they could always
try reporting it as a bug, but they should first know that the main
admin of the Fedora package is also frequently seen in the revision
history at gcc.gnu.org. One who is that deeply involved in the
development of GCC probably has a better idea of the differences
between versions than most of us do.
Björn Persson
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: comp.lang.ada

Keith Thompson <[email protected]> writes:

Simon Wright <[email protected]> writes:

Björn Persson <Bjorn@rombobjörn.se> writes:

It happened today in GCC 14.2.1 (as packaged in Fedora 41), so no, not
only in 14.2.0.

There's no official FSF 14.2.1 release - it may just be like Alire,
which only handles 3 levels, so they call the first packaging of 14.2.0
14.2.1. If you say 'gcc -v' it'll probably say 14.2.0.

Of course I could be completely wrong and Fedora have added lots of
value!

I see some potential for confusion, since there almost certainly will be
an official gcc 14.2.1 release in the near future. That official
release will include code that's not included in what Fedora calls gcc 14.2.1. It's a point release, so I wouldn't expect substantial changes,
but still, I think Fedora should use a different naming scheme.

After I wrote the above, I built gcc from its git repo, using the tip
of the releases/gcc-14 branch (not a release tag). Presumably the
Fedora folks did something similar. The resulting gcc reports its
own version as :

$ gcc --version
gcc (GCC) 14.2.1 20241129

whereas a gcc built from the releases/gcc-14.2.0 tag reports :

$ gcc --version
gcc (GCC) 14.2.0

with no date.

I still see some potential for confusion, but not as much as I initially thought. (The fact that gcc doesn't do *.*.1 releases is fairly
obscure, and I wouldn't expect most people to know about it.)
--
Keith Thompson (The_Other_Keith) [email protected]
void Void(void) { Void(); } /* The recursive call of the void */
--- Synchronet 3.20a-Linux NewsLink 1.114