public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Gaius Mulley <gaius@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/modula-2] Bugfix ensure that the scaffold source is kept if -fmakeinit present. Date: Wed, 2 Mar 2022 18:47:24 +0000 (GMT) [thread overview] Message-ID: <20220302184724.B5C97385842C@sourceware.org> (raw) https://gcc.gnu.org/g:8df4f2c9f53f43d59ccdb2ce3af180645ead8fa4 commit 8df4f2c9f53f43d59ccdb2ce3af180645ead8fa4 Author: q <gaius.mulley@southwales.ac.uk> Date: Wed Mar 2 18:46:13 2022 +0000 Bugfix ensure that the scaffold source is kept if -fmakeinit present. gcc/ChangeLog: * m2/m2-link-support.h (GEN_SCAFFOLD_SRC): New definition. (M2LINK) use GEN_SCAFFOLD_SRC to generate the scaffold name. Signed-off-by: <gaius.mulley@southwales.ac.uk> Diff: --- gcc/m2/m2-link-support.h | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/gcc/m2/m2-link-support.h b/gcc/m2/m2-link-support.h index a154e407cf1..eb52f2b4f0d 100644 --- a/gcc/m2/m2-link-support.h +++ b/gcc/m2/m2-link-support.h @@ -168,6 +168,13 @@ along with GCC; see the file COPYING3. If not see #define GM2(INPUT,OUTPUT) CC1GM2 " -o " OUTPUT " " INPUT +/* GEN_SCAFFOLD_SRC generates the string SCAFFOLDNAME ".cpp" + marking it for deletion if -fmakeinit is absent. */ + +#define GEN_SCAFFOLD_SRC \ + "%{fmakeinit:" SCAFFOLDNAME ".cpp;:" \ + SCAFFOLDNAME "%d.cpp}" + /* M2LINK compile main module (providing absense of -fonlylink) and link all project dependent modules. */ @@ -177,7 +184,7 @@ along with GCC; see the file COPYING3. If not see %{!fuselist:" GM2L("%i"," -o %g.l ") " \n\ " GM2LORDER("%g.l","%g.lst") " \n\ " GM2LGEN("%{fuselist:%b.lst;:%g.lst}",\ - "%{g:{!fmakeinit:%d}" SCAFFOLDNAME ".cpp;:%g.cpp}",\ + GEN_SCAFFOLD_SRC,\ "%d" SCAFFOLDNAME "%O") "}}\n\ }"
reply other threads:[~2022-03-02 18:47 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220302184724.B5C97385842C@sourceware.org \ --to=gaius@gcc.gnu.org \ --cc=gcc-cvs@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).