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 bootstrap/112534] [14 regression] build failure after r14-5424-gdb50aea6259545 using gcc 4.8.5
Date: Tue, 14 Nov 2023 23:23:09 +0000	[thread overview]
Message-ID: <bug-112534-4-XWUe0CUFCV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112534-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Hmm. similar issue happen with gdb 5 years ago:
https://lists.gnu.org/archive/html/bug-gnulib/2018-08/msg00151.html

Looks like this is huge gnulib mess at that.

  reply	other threads:[~2023-11-14 23:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 23:14 [Bug bootstrap/112534] New: " seurer at gcc dot gnu.org
2023-11-14 23:23 ` pinskia at gcc dot gnu.org [this message]
2023-11-15  0:57 ` [Bug bootstrap/112534] " bruno at clisp dot org
2023-11-15  1:03 ` bruno at clisp dot org
2023-11-15 11:58 ` rguenth at gcc dot gnu.org
2023-11-15 14:27 ` arsen at gcc dot gnu.org
2023-12-01 13:46 ` jakub at gcc dot gnu.org
2023-12-05 22:21 ` arsen at gcc dot gnu.org
2023-12-05 22:26 ` jakub at gcc dot gnu.org
2023-12-05 22:53 ` arsen at gcc dot gnu.org
2023-12-13 17:24 ` arsen at gcc dot gnu.org
2023-12-21  9:05 ` arsen at gcc dot gnu.org
2024-01-03  2:26 ` seurer at gcc dot gnu.org
2024-01-03 11:27 ` arsen at gcc dot gnu.org
2024-03-27 13:38 ` rguenth at gcc dot gnu.org
2024-03-27 18:47 ` arsen at gcc dot gnu.org
2024-05-07  7:42 ` [Bug bootstrap/112534] [14/15 " rguenth 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-112534-4-XWUe0CUFCV@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).