public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/31316] Fails test misc/tst-dirname "Didn't expect signal from child: got `Illegal instruction'" on non SSE CPUs Date: Fri, 16 Feb 2024 06:42:51 +0000 [thread overview] Message-ID: <bug-31316-131-5p13Hwk3bm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31316-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31316 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Flags| |security- Status|UNCONFIRMED |RESOLVED Target Milestone|--- |2.40 Assignee|unassigned at sourceware dot org |fweimer at redhat dot com --- Comment #10 from Florian Weimer <fweimer at redhat dot com> --- Fixed via: commit 0d9166c2245cad4ac520b337dee40c9a583872b6 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Feb 16 07:40:37 2024 +0100 i386: Use generic memrchr in libc (bug 31316) Before this change, we incorrectly used the SSE2 variant in the implementation, without checking that the system actually supports SSE2. Tested-by: Sam James <sam@gentoo.org> I have no immediate plans to handle the backports. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-16 6:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-30 3:05 [Bug build/31316] New: " immoloism at googlemail dot com 2024-01-30 3:06 ` [Bug build/31316] " immoloism at googlemail dot com 2024-01-30 3:19 ` immoloism at googlemail dot com 2024-01-30 3:22 ` immoloism at googlemail dot com 2024-01-30 11:55 ` fweimer at redhat dot com 2024-02-13 17:21 ` sam at gentoo dot org 2024-02-13 17:25 ` fweimer at redhat dot com 2024-02-13 17:27 ` sam at gentoo dot org 2024-02-13 17:28 ` sam at gentoo dot org 2024-02-13 17:41 ` sam at gentoo dot org 2024-02-13 17:42 ` sam at gentoo dot org 2024-02-13 17:48 ` fweimer at redhat dot com 2024-02-15 14:05 ` sam at gentoo dot org 2024-02-15 14:50 ` fweimer at redhat dot com 2024-02-16 6:42 ` fweimer at redhat dot com [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-31316-131-5p13Hwk3bm@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).