From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32545 invoked by alias); 17 May 2002 23:48:11 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 32518 invoked by uid 61); 17 May 2002 23:48:08 -0000 Date: Fri, 17 May 2002 16:48:00 -0000 Message-ID: <20020517234808.32517.qmail@sources.redhat.com> To: David.Decotigny@irisa.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org From: rth@gcc.gnu.org Reply-To: rth@gcc.gnu.org, David.Decotigny@irisa.fr, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: middle-end/6697: Unjustified (?) __attribute__ section conflicts X-SW-Source: 2002-05/txt/msg00534.txt.bz2 List-Id: Synopsis: Unjustified (?) __attribute__ section conflicts State-Changed-From-To: open->closed State-Changed-By: rth State-Changed-When: Fri May 17 16:48:07 2002 State-Changed-Why: Not a bug. "const int *p" is a non-constant variable that points to constant data; "const int i" is a constant variable. This "worked" in gcc 3.0 in that it did not diagnose the error. What would happen is that the assembler would use the type of the first variable assigned to the section to set the flags for the section. Which can appear random to users filing bug reports. So now all the variables assigned to a section must have the same section flags. I.e. all must be constant or all must be non-constant. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6697