public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108183] wrong code generated in the modula2 scaffold mechanism Date: Sun, 01 Jan 2023 09:29:36 +0000 [thread overview] Message-ID: <bug-108183-4-YXWIwaJm2G@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108183-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108183 --- Comment #18 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:d423e8dc59045d8f281dcb1a02559cb6f91456bf commit r13-4943-gd423e8dc59045d8f281dcb1a02559cb6f91456bf Author: Iain Sandoe <iain@sandoe.co.uk> Date: Wed Dec 21 09:05:32 2022 +0000 modula2: Ensure that module registration constructors are 'extern' [PR108183]. The symbols for module registration constructors need to be external or we get wrong code generated for targets that allow direct access to local symbol definitions. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> PR modula2/108183 gcc/m2/ChangeLog: * gm2-compiler/M2GCCDeclare.mod: Module registration constructors are externs to the builder of m2_link. Co-Authored-By: Gaius Mulley <gaiusmod2@gmail.com>
next prev parent reply other threads:[~2023-01-01 9:29 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-19 23:45 [Bug modula2/108183] New: " iains at gcc dot gnu.org 2022-12-19 23:46 ` [Bug modula2/108183] " iains at gcc dot gnu.org 2022-12-19 23:57 ` iains at gcc dot gnu.org 2022-12-20 8:20 ` gaius at gcc dot gnu.org 2022-12-20 8:38 ` gaius at gcc dot gnu.org 2022-12-20 9:36 ` iains at gcc dot gnu.org 2022-12-20 10:00 ` iains at gcc dot gnu.org 2022-12-20 12:34 ` iains at gcc dot gnu.org 2022-12-20 12:37 ` iains at gcc dot gnu.org 2022-12-20 12:45 ` rguenth at gcc dot gnu.org 2022-12-20 20:21 ` iains at gcc dot gnu.org 2022-12-20 20:42 ` iains at gcc dot gnu.org 2022-12-20 21:24 ` gaius at gcc dot gnu.org 2022-12-21 15:35 ` iains at gcc dot gnu.org 2022-12-21 15:39 ` iains at gcc dot gnu.org 2022-12-24 17:19 ` iains at gcc dot gnu.org 2022-12-28 16:07 ` gaius at gcc dot gnu.org 2022-12-31 12:54 ` iains at gcc dot gnu.org 2022-12-31 12:57 ` iains at gcc dot gnu.org 2023-01-01 9:29 ` cvs-commit at gcc dot gnu.org [this message] 2023-01-02 11:21 ` iains at gcc dot gnu.org 2023-01-02 12:20 ` iains at gcc dot gnu.org 2023-01-04 14:55 ` cvs-commit at gcc dot gnu.org 2023-01-04 16:22 ` iains 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-108183-4-YXWIwaJm2G@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: 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).