This is the mail archive of the
mailing list for the GCC project.
Re: GLOBAL constructor symbol names for static vars are bogus!
- To: bgarcia at fore dot com, egcs-bugs at cygnus dot com
- Subject: Re: GLOBAL constructor symbol names for static vars are bogus!
- From: mrs at wrs dot com (Mike Stump)
- Date: Fri, 20 Mar 1998 18:32:45 -0800
> X-Authentication-Warning: spud.eng.fore.com: bgarcia owned process doing -bs
> Date: Wed, 11 Mar 1998 09:50:56 -0500 (EST)
> From: "Brad M. Garcia" <email@example.com>
> X-Sender: firstname.lastname@example.org
> To: email@example.com
> However, most file names contain periods (ex - "foo.cc"). If I want
> to call one of these constructors myself (which I need to do in
> VxWorks, for example), gcc chokes on the name of the function because
> it contains a period.
munch from VxWorks is wrong. Sed the output of munch to use asm ("bla
bla") on the decls, and it should work. Or you can add a real decl to
> Can the names for these global constructors be "mangled" differently,
> or is there a way to get gcc to recognize the symbol in it's entirety,
> even though it contains periods?
I'm not in favor of that.