public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/106840] [13 Regression] glibc master build failure on ppc64le-linux-gnu since r13-2212-geb4879ab905308
Date: Tue, 06 Sep 2022 07:13:49 +0000 [thread overview]
Message-ID: <bug-106840-4-GH26mM6ooj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106840-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106840
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |13.0
Summary|glibc master build failure |[13 Regression] glibc
|on ppc64le-linux-gnu since |master build failure on
|r13-2212-geb4879ab905308 |ppc64le-linux-gnu since
| |r13-2212-geb4879ab905308
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, why does this C++ feature affect assembler source? The invocation
specifies -std=gnu11 so I would have expected the preprocessor to be set up in
"C mode"?
next prev parent reply other threads:[~2022-09-06 7:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 18:51 [Bug preprocessor/106840] New: " marxin at gcc dot gnu.org
2022-09-05 18:53 ` [Bug preprocessor/106840] " marxin at gcc dot gnu.org
2022-09-05 19:26 ` jakub at gcc dot gnu.org
2022-09-05 19:52 ` segher at gcc dot gnu.org
2022-09-06 4:05 ` marxin at gcc dot gnu.org
2022-09-06 7:13 ` rguenth at gcc dot gnu.org [this message]
2022-09-06 7:17 ` [Bug preprocessor/106840] [13 Regression] " jakub at gcc dot gnu.org
2022-09-06 7:55 ` marxin at gcc dot gnu.org
2022-10-19 6:11 ` rguenth at gcc dot gnu.org
2022-10-19 7:22 ` jakub at gcc dot gnu.org
2022-12-01 12:49 ` jakub at gcc dot gnu.org
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-106840-4-GH26mM6ooj@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).