This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

GLOBAL constructor symbol names for static vars are bogus!



When a file contains file-scope variables (defined static outside
of any functions), the name of the constructors for these variables
is based on the name of the file itself.

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.

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?

Brad Garcia
   ___/  __ /  __ /  ___/ "Being the Linux of digital media
  __/   /  /  / _/  __/    would be a very good life."
_/    ____/ _/ _| ____/      - Jean-Louis Gassee, CEO of Be, Inc.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]