This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: objc/6960: Compiler doesn't correct allocate object from -fconstant-string-class=
- From: nicola at sources dot redhat dot com
- To: daa at orcsoftware dot spb dot ru, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nicola at sources dot redhat dot com, nobody at gcc dot gnu dot org
- Date: 1 Sep 2002 12:22:13 -0000
- Subject: Re: objc/6960: Compiler doesn't correct allocate object from -fconstant-string-class=
- Reply-to: nicola at sources dot redhat dot com, daa at orcsoftware dot spb dot ru, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nicola at sources dot redhat dot com, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: Compiler doesn't correct allocate object from -fconstant-string-class=
Responsible-Changed-From-To: unassigned->nicola
Responsible-Changed-By: nicola
Responsible-Changed-When: Sun Sep 1 05:22:13 2002
Responsible-Changed-Why:
Looking at it
State-Changed-From-To: open->closed
State-Changed-By: nicola
State-Changed-When: Sun Sep 1 05:22:13 2002
State-Changed-Why:
The compiler is working properly. In the testcase, the
NSObject class contains an additional field _info in the
ivar layout, which causes NSConstantString to have an
additional ivar in the layout, which is not allowed.
I understand the point, but unfortunately this is not
supposed to work - the NSConstantString class ivar layout
is fixed. I also agree it should be documented better,
but that's it.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6960