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/27997] i386: CAN_USE_REGISTER_ASM_EBP is unreliable
Date: Mon, 10 Jan 2022 16:23:22 +0000 [thread overview]
Message-ID: <bug-27997-131-Jkjro43lTE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27997-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27997
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|I get an error when |i386:
|building glibc 2.33. |CAN_USE_REGISTER_ASM_EBP is
| |unreliable
CC| |drepper.fsp at gmail dot com
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=103646
Component|build |libc
--- Comment #13 from Florian Weimer <fweimer at redhat dot com> ---
GCC 12 with vectorization at -O2 makes this more visible.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-01-10 16:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 20:56 [Bug build/27997] New: I get an error when building glibc 2.33 xer8686 at mail dot ru
2021-06-19 21:04 ` [Bug build/27997] " xer8686 at mail dot ru
2021-06-22 4:08 ` adhemerval.zanella at linaro dot org
2021-06-22 10:30 ` fweimer at redhat dot com
2021-06-22 12:19 ` adhemerval.zanella at linaro dot org
2021-06-22 13:51 ` adhemerval.zanella at linaro dot org
2021-06-22 14:32 ` xer8686 at mail dot ru
2021-06-22 14:34 ` fweimer at redhat dot com
2021-06-22 14:44 ` xer8686 at mail dot ru
2021-06-22 14:59 ` adhemerval.zanella at linaro dot org
2021-06-22 15:07 ` xer8686 at mail dot ru
2021-08-15 20:50 ` xer8686 at mail dot ru
2021-08-19 12:17 ` adhemerval.zanella at linaro dot org
2022-01-10 16:23 ` fweimer at redhat dot com [this message]
2022-01-10 16:25 ` [Bug libc/27997] i386: CAN_USE_REGISTER_ASM_EBP is unreliable fweimer at redhat dot com
2022-01-13 14:23 ` fweimer at redhat dot com
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-27997-131-Jkjro43lTE@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: link
Be 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).