https://sourceware.org/bugzilla/show_bug.cgi?id=25295
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I was looking into the problem bit more. We want to support
__attribute__((symver("foo@VERS_1"))
int foo()
{
}
which will export foo as foo@VERS_1. I would also like things like calling foo
work as expected, i.e. call foo@VERS_1
Because foo@VERS_1 is not a valid name I need to produce other symbol name
(foo.symver1) that will be used at this place, but at the same time I do not
want it to be public in the .o symbol table and required to be explicitly
hidden by the user via map file (which seems to be common practice now).
--
You are receiving this mail because:
You are on the CC list for the bug.
