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 r13-5328] Bugfix ensure RTentity is a dependent of RTco.cc
Date: Tue, 24 Jan 2023 17:33:36 +0000 (GMT)	[thread overview]
Message-ID: <20230124173336.A098F3858C31@sourceware.org> (raw)

https://gcc.gnu.org/g:b061fc94d70dc82f554eeb94434cf03cd5af03f7

commit r13-5328-gb061fc94d70dc82f554eeb94434cf03cd5af03f7
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date:   Tue Jan 24 17:33:18 2023 +0000

    Bugfix ensure RTentity is a dependent of RTco.cc
    
    RTco is a definition for C module and therefore there is no
    RTco.mod.  The RTco.cc uses RTentity and the import in RTco.def
    ensures that cc1gm2 can build a graph of all dependencies
    should -fscaffold-static be used.
    
    gcc/m2/ChangeLog:
    
            * gm2-libs-iso/RTco.def: Import RTentity.
            Declare RTco as a definition for C module.
    
    Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>

Diff:
---
 gcc/m2/gm2-libs-iso/RTco.def | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/m2/gm2-libs-iso/RTco.def b/gcc/m2/gm2-libs-iso/RTco.def
index 33452bac990..5285a7deb10 100644
--- a/gcc/m2/gm2-libs-iso/RTco.def
+++ b/gcc/m2/gm2-libs-iso/RTco.def
@@ -24,10 +24,12 @@ a copy of the GCC Runtime Library Exception along with this program;
 see the files COPYING3 and COPYING.RUNTIME respectively.  If not, see
 <http://www.gnu.org/licenses/>.  *)
 
-DEFINITION MODULE RTco ;
+DEFINITION MODULE FOR "C" RTco ;
 
 FROM SYSTEM IMPORT ADDRESS ;
 
+IMPORT RTentity ;  (* Imported so the initialization call graph
+                      understands that RTco.cc depends upon RTentity.  *)
 
 (* init initializes the module and allows the application to lazily invoke threads.  *)

                 reply	other threads:[~2023-01-24 17:33 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=20230124173336.A098F3858C31@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: 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).