public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/34422] Bootstrap error with --enable-fixed-point (configure should reject --enable-fixed-point on platforms that don't support it) Date: Tue, 14 Jun 2022 19:52:16 +0000 [thread overview] Message-ID: <bug-34422-4-FmmUyyqGLC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-34422-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34422 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch URL| |https://gcc.gnu.org/piperma | |il/gcc-patches/2022-June/59 | |6654.html --- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> --- Patch posted to gcc-patches: https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596654.html
next prev parent reply other threads:[~2022-06-14 19:52 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-34422-4@http.gcc.gnu.org/bugzilla/> 2015-06-10 18:12 ` [Bug target/34422] Bootstrap error with --enable-fixed-point egall at gwmail dot gwu.edu 2020-11-20 22:43 ` egallager at gcc dot gnu.org 2022-05-24 15:07 ` [Bug target/34422] Bootstrap error with --enable-fixed-point (configure should reject --enable-fixed-point on platforms that don't support it) egallager at gcc dot gnu.org 2022-05-24 15:19 ` egallager at gcc dot gnu.org 2022-05-25 1:57 ` egallager at gcc dot gnu.org 2022-05-25 2:15 ` egallager at gcc dot gnu.org 2022-06-14 19:52 ` egallager at gcc dot gnu.org [this message] 2022-07-07 23:22 ` egallager at gcc dot gnu.org 2023-08-25 13:24 ` egallager 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-34422-4-FmmUyyqGLC@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).