public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/111756] Re-building all-gcc after source changes fails to link
Date: Tue, 17 Oct 2023 10:18:48 +0000 [thread overview]
Message-ID: <bug-111756-4-611WxmHzeq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111756-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111756
Gaius Mulley <gaius at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #56122|0 |1
is obsolete| |
--- Comment #4 from Gaius Mulley <gaius at gcc dot gnu.org> ---
Created attachment 56132
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56132&action=edit
Proposed fix v6, Make-lang.in uses -M and friends, gm2 and cc1gm2 implement -M*
Here is a proposed fix and patch, the Make-lang.in now uses dependencies and
gm2 cc1gm2 understands all the -M* options. Bootstrapped on x86_64 and
powerpc64le with no extra regression failures.
I've also seen it re-build with the BuildInline procedure introduced to
M2Quads.mod (rebuild). Introduce BuildInline into M2Quads.def and P3Build.bnf.
Rebuild (seeing M2Quads.mod rebuild due to dependencies).
next prev parent reply other threads:[~2023-10-17 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 7:09 [Bug modula2/111756] New: " rguenth at gcc dot gnu.org
2023-10-11 20:12 ` [Bug modula2/111756] " gaius at gcc dot gnu.org
2023-10-15 1:29 ` gaius at gcc dot gnu.org
2023-10-16 17:19 ` gaius at gcc dot gnu.org
2023-10-17 10:18 ` gaius at gcc dot gnu.org [this message]
2023-10-17 13:12 ` cvs-commit at gcc dot gnu.org
2023-10-17 13:13 ` gaius at gcc dot gnu.org
2023-10-17 13:15 ` gaius at gcc dot gnu.org
2023-10-18 2:06 ` gaius at gcc dot gnu.org
2023-10-18 2:10 ` cvs-commit at gcc dot gnu.org
2023-10-18 2:11 ` gaius 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-111756-4-611WxmHzeq@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).