[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-bugs
Subject:    [Bug modula2/108183] wrong code generated in the modula2 scaffold mechanism
From:       "iains at gcc dot gnu.org via Gcc-bugs" <gcc-bugs () gcc ! gnu ! org>
Date:       2022-12-31 12:57:17
Message-ID: bug-108183-4-7JBU7Q2tV3 () http ! gcc ! gnu ! org/bugzilla/
[Download RAW message or body]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108183

--- Comment #17 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #16)
> Created attachment 54170 [details]
> Patch registration constructors
> 
> This modifies the registration CTORs that are currently defined in C++ to be
> defined as 'extern "C"' and registered to be run at program load time.
> 
> This is as described in comments #14 and 15.

I did not post this yet - because I was wondering if there is more needed

 (i.e. that the code-gen should also do something similar when .mods are
compiled).  For example, if I take a random test case, and examine the symbols
- I see these CTORs - but I do not see any CTORs for non-library modules.

Of course, that could also be a separate patch - don't think I know the m2
sources well enough to attempt it at present, tho.=
[prev in list] [next in list] [prev in thread] [next in thread]