James E Wilson <[EMAIL PROTECTED]> writes: >> unnecessary, and error prone (as evidenced by string literal memory >> references not being properly identified as READONLY, although their >> equivalent array representations are treated properly for example?) > > If true, that sounds like a bug. This is the only interesting issue > here from my point of view. You might consider filing a bug report into > bugzilla for this. Or contributing a patch.
This might just be the special case for string constants in C, that their type is "char*" despite their being allocated in read-only memory. Paul, before filing a bug, find out whether -Wwrite-strings makes this alleged misbehavior go away; if it does, it's not a bug. zw
