public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
* Please backport some GCC 13 build fixes
@ 2022-11-19 18:55 WANG Xuerui
  2022-11-19 20:09 ` Andreas K. Huettel
  0 siblings, 1 reply; 4+ messages in thread
From: WANG Xuerui @ 2022-11-19 18:55 UTC (permalink / raw)
  To: libc-stable; +Cc: Joseph Myers, toolchain


[-- Attachment #1.1.1: Type: text/plain, Size: 680 bytes --]

Hi,

As it's entirely possible for users to pair the upcoming gcc-13 with one 
of the older glibc versions, it may be prudent to backport at least the 
following commits so builds won't fail in such cases:

  * 3e5760fcb4 ("Update _FloatN header support for C++ in GCC 13")
  * ba70f69598 ("Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13")
  * f66780ba46 ("Fix build with GCC 13 _FloatN, _FloatNx built-in
    functions")

Thanks!

(P.S. I don't have glibc commit rights so someone else would have to 
commit for me. Sorry about that.)

-- 
WANG Xuerui
xen0n@gentoo.org
Gentoo Linux developer
PGP: 7C52 19E3 26A0 7311 3EA3 8806 C01F 7214 BC93 1414


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 23337 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Please backport some GCC 13 build fixes
  2022-11-19 18:55 Please backport some GCC 13 build fixes WANG Xuerui
@ 2022-11-19 20:09 ` Andreas K. Huettel
  2022-11-21 20:37   ` Joseph Myers
  0 siblings, 1 reply; 4+ messages in thread
From: Andreas K. Huettel @ 2022-11-19 20:09 UTC (permalink / raw)
  To: libc-stable, WANG Xuerui; +Cc: Joseph Myers, toolchain

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

>   * 3e5760fcb4 ("Update _FloatN header support for C++ in GCC 13")
>   * ba70f69598 ("Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13")
>   * f66780ba46 ("Fix build with GCC 13 _FloatN, _FloatNx built-in
>     functions")

FWIW, I added these three commits to our 2.36 and got some FP test failures
requiring distinct changes in ulps.

Hardware / software: 
Linux pinacolada 5.19.17-gentoo #1 SMP PREEMPT_DYNAMIC Sun Nov 6 20:29:37 CET 2022 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux
gcc (Gentoo 11.3.0 p7) 11.3.0

Failure summary:
FAIL: math/test-double-j0
FAIL: math/test-float-ctan
FAIL: math/test-float-j1
FAIL: math/test-float-y0
FAIL: math/test-float-y1
FAIL: math/test-float32-ctan
FAIL: math/test-float32-j1
FAIL: math/test-float32-y0
FAIL: math/test-float32-y1
FAIL: math/test-float32x-j0
FAIL: math/test-float64-j0

Patch produced by regen-ulps:

diff --git a/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps b/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps
index 284e3fa275..8705a7822c 100644
--- a/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps
+++ b/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps
@@ -1027,7 +1027,7 @@ ldouble: 3
 
 Function: Imaginary part of "ctan_upward":
 double: 2
-float: 1
+float: 2
 float128: 5
 ldouble: 3
 
@@ -1260,13 +1260,13 @@ float128: 2
 ldouble: 8
 
 Function: "j0_downward":
-double: 5
+double: 6
 float: 9
 float128: 9
 ldouble: 6
 
 Function: "j0_towardzero":
-double: 6
+double: 7
 float: 9
 float128: 9
 ldouble: 6
@@ -1285,13 +1285,13 @@ ldouble: 9
 
 Function: "j1_downward":
 double: 5
-float: 6
+float: 8
 float128: 4
 ldouble: 4
 
 Function: "j1_towardzero":
 double: 4
-float: 6
+float: 8
 float128: 4
 ldouble: 4
 
@@ -1617,7 +1617,7 @@ ldouble: 5
 
 Function: "y0_towardzero":
 double: 4
-float: 4
+float: 8
 float128: 3
 ldouble: 8
 
@@ -1641,7 +1641,7 @@ ldouble: 7
 
 Function: "y1_towardzero":
 double: 3
-float: 4
+float: 9
 float128: 6
 ldouble: 5
 


-- 
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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Please backport some GCC 13 build fixes
  2022-11-19 20:09 ` Andreas K. Huettel
@ 2022-11-21 20:37   ` Joseph Myers
  2022-11-27 14:35     ` [Disregard my previous mail] " Andreas K. Huettel
  0 siblings, 1 reply; 4+ messages in thread
From: Joseph Myers @ 2022-11-21 20:37 UTC (permalink / raw)
  To: Andreas K. Huettel; +Cc: libc-stable, WANG Xuerui, toolchain

On Sat, 19 Nov 2022, Andreas K. Huettel via Libc-stable wrote:

> >   * 3e5760fcb4 ("Update _FloatN header support for C++ in GCC 13")
> >   * ba70f69598 ("Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13")
> >   * f66780ba46 ("Fix build with GCC 13 _FloatN, _FloatNx built-in
> >     functions")
> 
> FWIW, I added these three commits to our 2.36 and got some FP test failures
> requiring distinct changes in ulps.

These aren't meant to change the code generated for glibc (with any given 
GCC version that worked for building glibc before those changes, so GCC 12 
or before) at all, so it would be a good idea to investigate why the 
generated code changed.

-- 
Joseph S. Myers
joseph@codesourcery.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Disregard my previous mail] Re: Please backport some GCC 13 build fixes
  2022-11-21 20:37   ` Joseph Myers
@ 2022-11-27 14:35     ` Andreas K. Huettel
  0 siblings, 0 replies; 4+ messages in thread
From: Andreas K. Huettel @ 2022-11-27 14:35 UTC (permalink / raw)
  To: Joseph Myers; +Cc: libc-stable, WANG Xuerui, toolchain

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

Am Montag, 21. November 2022, 21:37:18 CET schrieb Joseph Myers:
> On Sat, 19 Nov 2022, Andreas K. Huettel via Libc-stable wrote:
> 
> > >   * 3e5760fcb4 ("Update _FloatN header support for C++ in GCC 13")
> > >   * ba70f69598 ("Fix iseqsig for _FloatN and _FloatNx in C++ with GCC 13")
> > >   * f66780ba46 ("Fix build with GCC 13 _FloatN, _FloatNx built-in
> > >     functions")
> > 
> > FWIW, I added these three commits to our 2.36 and got some FP test failures
> > requiring distinct changes in ulps.
> 
> These aren't meant to change the code generated for glibc (with any given 
> GCC version that worked for building glibc before those changes, so GCC 12 
> or before) at all, so it would be a good idea to investigate why the 
> generated code changed.

My apologies; this was *not* caused by the three commits listed above.
So, from my point of view there are no problems at all with backporting them.

The changes which broke the tests must have crept into the/our release branch
earlier. Searching.

-- 
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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-11-27 14:36 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-19 18:55 Please backport some GCC 13 build fixes WANG Xuerui
2022-11-19 20:09 ` Andreas K. Huettel
2022-11-21 20:37   ` Joseph Myers
2022-11-27 14:35     ` [Disregard my previous mail] " Andreas K. Huettel

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).