This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/21018] Initializing string literal data improperly marked frame-relative?, should be readonly static const.
- From: "schlie at comcast dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 16 Apr 2005 18:22:10 -0000
- Subject: [Bug middle-end/21018] Initializing string literal data improperly marked frame-relative?, should be readonly static const.
- References: <20050414064455.21018.schlie@comcast.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From schlie at comcast dot net 2005-04-16 18:22 -------
Subject: Re: Initializing string literal data
improperly marked frame-relative?, should be readonly static const.
> Note the C.x variables are not normal VAR_DECLs but CONST_DECL so maybe avr
> should be changed to recongize them as such.
Actually the problem seems then be that literal string constants aren't
being consistently defined through CONST_DECL's (just as initializing char
array data, which are equivalent to string initializers, and all other
literal and static constants which end up being stored as literal data are);
for which MEM_READONLY_P allows all memory references to, to be easily
identified, which seems to be it's intent.
Is there any reason that literal string constant data shouldn't be similarly
declared and correspondingly identifiable? (or just an oversight?)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21018