Please use --enable-fortify-source when testing

Please use --enable-fortify-source when testing

[Andreas K. Huettel]

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

Dear all, 

the 2.38 release date and with it a hard cutoff for fixes is coming closer and
closer. Still, if you are doing machine testing, 

** Please use --enable-fortify-source **

We need more data on possible compiler/binutils/architecture... combinations there.

Thanks!
Andreas

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

Re: Please use --enable-fortify-source when testing

[Adhemerval Zanella Netto]

On 26/07/23 06:30, Andreas K. Huettel via Libc-alpha wrote:
> Dear all, 
> 
> the 2.38 release date and with it a hard cutoff for fixes is coming closer and
> closer. Still, if you are doing machine testing, 
> 
> ** Please use --enable-fortify-source **
> 
> We need more data on possible compiler/binutils/architecture... combinations there.

With my patches to fix old gcc build [1][2] and i686 with fortify [3], I checked
full builds for aarch64, x86_64, i686, s390x, powerpc64, and mips64 for with all 
supported gcc (from 6 to 13, it vary depending of the architecture) with default
no fortify and with fortify from 1 to 3 (if compiler supports it).  I have not
found issues, although I only run check for x86 so far.

I might try some more architectures, although I don't expect more failures.

[1] https://patchwork.sourceware.org/project/glibc/list/?series=22751
[2] https://patchwork.sourceware.org/project/glibc/list/?series=22754
[3] https://patchwork.sourceware.org/project/glibc/list/?series=22775

Re: Please use --enable-fortify-source when testing

[Carlos O'Donell]

On 7/26/23 08:53, Adhemerval Zanella Netto via Libc-alpha wrote:
> 
> 
> On 26/07/23 06:30, Andreas K. Huettel via Libc-alpha wrote:
>> Dear all, 
>>
>> the 2.38 release date and with it a hard cutoff for fixes is coming closer and
>> closer. Still, if you are doing machine testing, 
>>
>> ** Please use --enable-fortify-source **
>>
>> We need more data on possible compiler/binutils/architecture... combinations there.
> 
> With my patches to fix old gcc build [1][2] and i686 with fortify [3], I checked
> full builds for aarch64, x86_64, i686, s390x, powerpc64, and mips64 for with all 
> supported gcc (from 6 to 13, it vary depending of the architecture) with default
> no fortify and with fortify from 1 to 3 (if compiler supports it).  I have not
> found issues, although I only run check for x86 so far.
> 
> I might try some more architectures, although I don't expect more failures.
> 
> [1] https://patchwork.sourceware.org/project/glibc/list/?series=22751
> [2] https://patchwork.sourceware.org/project/glibc/list/?series=22754
> [3] https://patchwork.sourceware.org/project/glibc/list/?series=22775

Thank you Adhemerval for doing all of this testing! It is really awesome.

I'm testing on x86_64, i686, aarch64, s390x, and ppc64le right now with
gcc 13 (Fedora 39), 11 (RHEL9), and 8 (RHEL8) with a variety of binutils.

I am rechecking again with --enable-fortify-source.

-- 
Cheers,
Carlos.

Re: Please use --enable-fortify-source when testing

[Andreas K. Huettel]

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

Am Donnerstag, 27. Juli 2023, 04:10:57 CEST schrieb Carlos O'Donell via Libc-alpha:
> On 7/26/23 08:53, Adhemerval Zanella Netto via Libc-alpha wrote:
> > 
> > With my patches to fix old gcc build [1][2] and i686 with fortify [3], I checked
> > full builds for aarch64, x86_64, i686, s390x, powerpc64, and mips64 for with all 
> > supported gcc (from 6 to 13, it vary depending of the architecture) with default
> > no fortify and with fortify from 1 to 3 (if compiler supports it).  I have not
> > found issues, although I only run check for x86 so far.
> > 
> > I might try some more architectures, although I don't expect more failures.
> > 
> > [1] https://patchwork.sourceware.org/project/glibc/list/?series=22751
> > [2] https://patchwork.sourceware.org/project/glibc/list/?series=22754
> > [3] https://patchwork.sourceware.org/project/glibc/list/?series=22775
> 
> Thank you Adhemerval for doing all of this testing! It is really awesome.
> 
> I'm testing on x86_64, i686, aarch64, s390x, and ppc64le right now with
> gcc 13 (Fedora 39), 11 (RHEL9), and 8 (RHEL8) with a variety of binutils.
> 
> I am rechecking again with --enable-fortify-source.

Great, thanks a lot to you both!

-- 
PD Dr. Andreas K. Huettel
Institute for Experimental and Applied Physics
University of Regensburg
93040 Regensburg
Germany

tel. +49 151 241 67748 (mobile)
tel. +49 941 943 1618 (office)
e-mail andreas.huettel@ur.de
https://www.akhuettel.de/
https://www.akhuettel.de/group/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]