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 libc/28680] i686 builds broken with -ftree-vectorize Date: Mon, 10 Jan 2022 16:25:46 +0000 [thread overview] Message-ID: <bug-28680-131-rfFYijqSV5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28680-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28680 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|build |libc Flags| |security- Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC| |drepper.fsp at gmail dot com --- Comment #3 from Florian Weimer <fweimer at redhat dot com> --- Let's track this under the earlier bug. *** This bug has been marked as a duplicate of bug 27997 *** -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-01-10 16:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-10 16:48 [Bug build/28680] New: " siddhesh at sourceware dot org 2021-12-10 16:49 ` [Bug build/28680] " siddhesh at sourceware dot org 2021-12-10 17:01 ` fweimer at redhat dot com 2021-12-10 17:48 ` siddhesh at sourceware dot org 2022-01-10 16:25 ` 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-28680-131-rfFYijqSV5@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).