This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug ada/66205] gnatbind generates invalid code when finalization is enabled in restricted runtime
- From: "simon at pushface dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 11 Jun 2015 15:59:35 +0000
- Subject: [Bug ada/66205] gnatbind generates invalid code when finalization is enabled in restricted runtime
- Auto-submitted: auto-generated
- References: <bug-66205-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66205
--- Comment #4 from simon at pushface dot org ---
Agree itâs not ARM-specific, but it _is_ Ada-restricted-runtime-specific.
I realise that this isnât a configuration supported by AdaCore for their
customers (thereâd have been no need for this PR if it was!); does it have to
be unsupported by GCC then?
Iâve managed to make what I think is a very-low-quality workround by
(a) not suppressing the standard library on the target in system.ads
(b) including a C source file in the RTS which provides dummies for the
irrelevant-in-this-context __gl_* objects which bindgen now references.
Anyway, now I have my copyright assignment in place, Iâll submit the patch. Iâm
not sure what regression tests would be appropriate: I propose to apply the
patch and bootstrap/make check-ada for Darwin, that will show I havenât broken
the normal case, and I can repeat the build for arm-eabi and build a null main
program.
If thereâs no chance that this patch will ever be accepted, please let me know
before I embark on this!