This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/55617] static constructors are not being instrumented correctly on darwin
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 30 Jan 2013 16:43:03 +0000
- Subject: [Bug sanitizer/55617] static constructors are not being instrumented correctly on darwin
- Auto-submitted: auto-generated
- References: <bug-55617-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55617
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-30 16:43:03 UTC ---
Well, if somebody does the work and in a clean way that won't penalize targets
with sane linkers and object formats, I'm not objecting, I just am not going to
spend time on this. If clang can handle ctor priorities right at least inside
of each individual CUs, perhaps those that care about targets which don't
support that in the linker can add similar support to gcc (what I've been
suggesting, if priorities aren't supported by linker, don't emit stuff right
away, but just queue it and at the end sort it and emit.