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: Fri, 25 Aug 2023 13:24:31 +0000 [thread overview]
Message-ID: <bug-34422-4-hhzXKQVBiK@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
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|egallager at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #12)
> (In reply to Eric Gallager from comment #11)
> > Patch posted to gcc-patches:
> > https://gcc.gnu.org/pipermail/gcc-patches/2022-June/596654.html
>
> So this patch needs some more work; it might take awhile before I get to
> fixing it though... should I unassign? I still intend to get back to this
> later, but I just want to make sure that people are clear that they can give
> it a try themselves in the meantime...
...ok yeah I think I'm going to unassign; if anyone thinks they can address the
feedback from here, feel free to take it:
https://gcc.gnu.org/pipermail/gcc-patches/2022-June/597046.html
prev parent reply other threads:[~2023-08-25 13:24 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
2022-07-07 23:22 ` egallager at gcc dot gnu.org
2023-08-25 13:24 ` egallager at gcc dot gnu.org [this message]
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-hhzXKQVBiK@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).