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 bootstrap/112534] [14 regression] build failure after r14-5424-gdb50aea6259545 using gcc 4.8.5
Date: Wed, 27 Mar 2024 13:38:21 +0000 [thread overview]
Message-ID: <bug-112534-4-uu6pLh9HkS@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
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2024-03-27
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |arsen at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
Looks like the patch is still not reviewed. I haven't had issues with using
system gettext though.
next prev parent reply other threads:[~2024-03-27 13:38 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 ` [Bug bootstrap/112534] " pinskia at gcc dot gnu.org
2023-11-15 0:57 ` 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 [this message]
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-uu6pLh9HkS@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).