public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104859] [12 regression] liibg++ fails during bootstrap
Date: Wed, 09 Mar 2022 21:45:07 +0000 [thread overview]
Message-ID: <bug-104859-4-6AYGkpU31h@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104859-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104859
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to seurer from comment #3)
> stage 1. It happens on a non-bootstrap, too.
I was worried that it was causing wrong code in the front-end.
Can you attach the preprocessed source for floating_to_chars.cc ?
next prev parent reply other threads:[~2022-03-09 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:18 [Bug libgcc/104859] New: " seurer at gcc dot gnu.org
2022-03-09 21:31 ` [Bug libgcc/104859] " seurer at gcc dot gnu.org
2022-03-09 21:38 ` [Bug c++/104859] " pinskia at gcc dot gnu.org
2022-03-09 21:42 ` seurer at gcc dot gnu.org
2022-03-09 21:45 ` pinskia at gcc dot gnu.org [this message]
2022-03-09 22:09 ` ppalka at gcc dot gnu.org
2022-03-09 22:10 ` jakub at gcc dot gnu.org
2022-03-09 22:12 ` jakub at gcc dot gnu.org
2022-03-09 23:49 ` [Bug libstdc++/104859] " cvs-commit at gcc dot gnu.org
2022-03-10 0:04 ` ppalka at gcc dot gnu.org
2022-03-10 8:41 ` [Bug libstdc++/104859] [11 Regression] libg++ " rguenth at gcc dot gnu.org
2022-04-07 10:13 ` rguenth at gcc dot gnu.org
2022-04-07 15:41 ` redi at gcc dot gnu.org
2022-04-07 19:36 ` cvs-commit at gcc dot gnu.org
2022-04-07 19:38 ` ppalka 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-104859-4-6AYGkpU31h@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).