public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/111664] [14 regression] Fails to build with mawk (error in gcc/opt-read.awk) after r14-4354-ge4a4b8e983bac8 Date: Wed, 04 Oct 2023 14:37:49 +0000 [thread overview] Message-ID: <bug-111664-4-eOCfiBJ5VD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111664-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111664 David Binderman <dcb314 at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcb314 at hotmail dot com --- Comment #5 from David Binderman <dcb314 at hotmail dot com> --- I saw this also on a raspberry pi that uses mawk. I think there is still some value in testing patches in a couple of very different places to help increase portability of code. After the correcting patch, all appears to be in order on the pi.
next prev parent reply other threads:[~2023-10-04 14:37 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-02 15:47 [Bug bootstrap/111664] New: [14 regression] error in gcc/opt-read.awk " seurer at gcc dot gnu.org 2023-10-02 15:50 ` [Bug bootstrap/111664] " sjames at gcc dot gnu.org 2023-10-02 19:24 ` [Bug bootstrap/111664] [14 regression] Fails to build with mawk (error in gcc/opt-read.awk) " seurer at gcc dot gnu.org 2023-10-03 2:33 ` kito at gcc dot gnu.org 2023-10-04 9:42 ` rguenth at gcc dot gnu.org 2023-10-04 13:38 ` cvs-commit at gcc dot gnu.org 2023-10-04 14:37 ` dcb314 at hotmail dot com [this message] 2023-10-07 20:56 ` law 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-111664-4-eOCfiBJ5VD@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: linkBe 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).