public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108183] New: wrong code generated in the modula2 scaffold mechanism Date: Mon, 19 Dec 2022 23:45:42 +0000 [thread overview] Message-ID: <bug-108183-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108183 Bug ID: 108183 Summary: wrong code generated in the modula2 scaffold mechanism Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: modula2 Assignee: gaius at gcc dot gnu.org Reporter: iains at gcc dot gnu.org Target Milestone: --- On m32 Darwin, we see very many failures like: /Volumes/ramdisk/ccPnX6B8.s:379:non-relocatable subtraction expression, "__M2_dtoa_ctor" minus "L5$pb" /Volumes/ramdisk/ccPnX6B8.s:379:symbol: "__M2_dtoa_ctor" can't be undefined in a subtraction expression === It seems that the function declarations for '__M2_dtoa_ctor' (and other imported module ctors) are declared with TREE_STATIC() set, which indicates that there is a definition in the TU (which there is not) - they should be declared as external. So far, I could not figure out where these decls are built and what controls whether they are considered external or not.
next reply other threads:[~2022-12-19 23:45 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-19 23:45 iains at gcc dot gnu.org [this message] 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 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@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).