public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111632] gcc fails to bootstrap when using libc++
Date: Thu, 09 May 2024 12:12:05 +0000	[thread overview]
Message-ID: <bug-111632-4-vJDbDcKg7j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111632-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111632

--- Comment #31 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Liviu Ionescu from comment #30)
> (In reply to Dimitry Andric from comment #29)
> > ... fixes system.h which is also included by gcov.cc
> 
> ok, great.
> 
> > Which version of gcc were you building?
> 
> in the reported bug I was building 13.2.
> 
> was the fix backported to older versions?

so far, the fix has baeen back ported for 13.3 .. it is on the list to be back
ported for 12.4 and 11.5,

  parent reply	other threads:[~2024-05-09 12:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-28 16:26 [Bug other/111632] New: gcc's C++ components fail to compile against recent libc++ headers dimitry at andric dot com
2023-09-28 16:26 ` [Bug other/111632] " dimitry at andric dot com
2023-09-29  8:37 ` [Bug middle-end/111632] " rguenth at gcc dot gnu.org
2023-09-29  8:49 ` dimitry at andric dot com
2023-10-05 23:44 ` [Bug middle-end/111632] gcc fails to bootstrap when using libc++ pinskia at gcc dot gnu.org
2023-10-26 16:46 ` dimitry at andric dot com
2023-10-26 16:52 ` sjames at gcc dot gnu.org
2024-02-08 10:56 ` arsen at gcc dot gnu.org
2024-02-08 11:00 ` jakub at gcc dot gnu.org
2024-02-08 12:34 ` arsen at gcc dot gnu.org
2024-02-29 15:10 ` dimitry at andric dot com
2024-03-06 13:38 ` fxcoudert at gcc dot gnu.org
2024-03-06 13:48 ` redi at gcc dot gnu.org
2024-03-06 20:05 ` iains at gcc dot gnu.org
2024-03-06 20:15 ` dimitry@unified-streaming.com
2024-03-06 20:18 ` iains at gcc dot gnu.org
2024-03-06 22:51 ` dimitry at andric dot com
2024-03-06 22:52 ` dimitry at andric dot com
2024-03-07 13:41 ` fxcoudert at gcc dot gnu.org
2024-03-07 18:55 ` dimitry@unified-streaming.com
2024-03-29 19:41 ` iains at gcc dot gnu.org
2024-03-29 20:18 ` dimitry at andric dot com
2024-03-29 23:30 ` gerald at pfeifer dot com
2024-03-30  6:14 ` iains at gcc dot gnu.org
2024-04-03 14:48 ` cvs-commit at gcc dot gnu.org
2024-04-03 14:49 ` cvs-commit at gcc dot gnu.org
2024-04-03 14:50 ` iains at gcc dot gnu.org
2024-05-09 11:17 ` fxcoudert at gcc dot gnu.org
2024-05-09 11:30 ` ilg at livius dot net
2024-05-09 11:47 ` dimitry at andric dot com
2024-05-09 12:07 ` ilg at livius dot net
2024-05-09 12:12 ` iains at gcc dot gnu.org [this message]
2024-05-09 12:12 ` jakub at gcc dot gnu.org
2024-05-09 12:34 ` ilg at livius dot net

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-111632-4-vJDbDcKg7j@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).