public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/112825] Modula 2 builds target objects as part of all-gcc
Date: Sun, 03 Dec 2023 23:14:23 +0000 [thread overview]
Message-ID: <bug-112825-4-QYbsCtD5o4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112825-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112825
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tschwinge at gcc dot gnu.org
--- Comment #4 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
I too, months ago, had run into this problem -- via the nvptx 'as' failing on
'-o /dev/null'... (which I'll fix anyway). After a quick look at
'gcc/m2/tools-src/makeSystem' I did presume that the compiler is invoked there
only for some side effects (remember, '-o /dev/null'), and thus fixing this
might be...
(In reply to Gaius Mulley from comment #3)
> Created attachment 56782 [details]
> Proposed fix
>
> This patch changes all invocations of gm2 -c to gm2 -S to avoid invoking the
> target assembler (which might not be present if make all-gcc is run).
... as simple as this. (Then, of course, interrupted by higher-priority
things, and I never got back to this.)
Therefore, for what it's worth, conceptual ACK to this proposed change (which
I've not yet tested, but will, eventually).
next prev parent reply other threads:[~2023-12-03 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 14:23 [Bug modula2/112825] New: " rsandifo at gcc dot gnu.org
2023-12-02 21:19 ` [Bug modula2/112825] " gaius at gcc dot gnu.org
2023-12-03 22:19 ` gaius at gcc dot gnu.org
2023-12-03 22:25 ` gaius at gcc dot gnu.org
2023-12-03 23:14 ` tschwinge at gcc dot gnu.org [this message]
2023-12-04 1:36 ` cvs-commit at gcc dot gnu.org
2023-12-04 1:39 ` 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-112825-4-QYbsCtD5o4@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).