[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-04-30 Thread Bug Watch Updater
** Changed in: evolver (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929 Title: failed autopkgtests for evolver vs glibc 2.39 on amd64 To manage

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-04-06 Thread Bug Watch Updater
** Changed in: gcc Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929 Title: failed autopkgtests for evolver vs glibc 2.39 on amd64 To manage notifications

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-04-05 Thread Launchpad Bug Tracker
This bug was fixed in the package gcc-13 - 13.2.0-23ubuntu3 --- gcc-13 (13.2.0-23ubuntu3) noble; urgency=medium * Use gcc:SoftVersion for -for-host dependencies (Helmut Grohne). Addresses: #1067904. * Apply proposed patch for PR libquadmath/114533 (Simon Chopin).

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-04-02 Thread Launchpad Bug Tracker
This bug was fixed in the package gcc-14 - 14-20240330-1ubuntu2 --- gcc-14 (14-20240330-1ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek Sun, 31 Mar 2024 01:02:56 + ** Changed in: gcc-14 (Ubuntu) Status: In Progress => Fix

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-30 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-30 Thread Matthias Klose
** Bug watch added: GCC Bugzilla #114533 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 ** Also affects: gcc via https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114533 Importance: Unknown Status: Unknown ** Changed in: gcc-14 (Ubuntu) Status: New => In Progress -- You

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-30 Thread Matthias Klose
** Also affects: gcc-13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929 Title: failed autopkgtests for evolver vs glibc 2.39 on amd64 To

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-28 Thread Simon Chopin
** Changed in: glibc (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929 Title: failed autopkgtests for evolver vs glibc 2.39 on amd64 To manage

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-12 Thread Simon Chopin
Using the PPA's libquadmath makes the tests pass, so I sent the patch upstream: https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647635.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-12 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052929 Title: failed autopkgtests for evolver vs glibc 2.39 on amd64 To manage notifications about this bug go to:

[Bug 2052929] Re: failed autopkgtests for evolver vs glibc 2.39 on amd64

2024-03-12 Thread Simon Chopin
This bug is actually in gcc-14, more specifically libquadmath, as they do a misaligned read from args to a float128, which produces the segfault. It was hidden so far because args was allocated using alloca() which I guess must be naturally aligned, but in 2.39 they removed that in favor of