This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/41091] Using section attribute in c and c++ function causes section type conflict
- From: "mark at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Oct 2009 07:48:37 -0000
- Subject: [Bug c++/41091] Using section attribute in c and c++ function causes section type conflict
- References: <bug-41091-3639@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from mark at gcc dot gnu dot org 2009-10-14 07:48 -------
(In reply to comment #1)
> Actually, they have to have two different section types.
>
> c::m()::TWO has to be in the comdat section for C::m().
> While c()::ONE does not and can be in a normal section.
INVALID? How is the user supposed to know (or care) about comdat? All they want
is make sure the constants get put in the same section. So how can one specify
that behavior for both ONE and TWO?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41091