From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17846 invoked by alias); 14 Oct 2009 07:48:50 -0000 Received: (qmail 17796 invoked by uid 48); 14 Oct 2009 07:48:37 -0000 Date: Wed, 14 Oct 2009 07:48:00 -0000 Message-ID: <20091014074837.17795.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/41091] Using section attribute in c and c++ function causes section type conflict In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "mark at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2009-10/txt/msg01192.txt.bz2 ------- 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