This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Reload Issue -- I can't believe we haven't hit this before
- From: Paul Schlie <schlie at comcast dot net>
- To: Eric Botcazou <ebotcazou at libertysurf dot fr>,<law at redhat dot com>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Tue, 19 Apr 2005 14:03:12 -0400
- Subject: Re: Reload Issue -- I can't believe we haven't hit this before
> From: Paul Schlie <schlie@comcast.net>
>
> some-const-char*-funct("abc"); // "C.x[4] = {'a','b','c',0} array
> // of "literal static const data"
> // some-const-char*-funct(C.x);
Or rather I suspect it implies the allocation of a temporary to store
C.x[] into then passing the reference to the temporary (as there seems to
be no present way to define a function parameter which points to a "literal
static const data" object, vs. a generic allocated const object, because
although "static const char s[]" may denote an array of "literal static
const data", funct(static const char *) is interpreted as attempting to
declare the storage class of the pointer parameter, as opposed to qualifying
the storage class of the object it's pointing to)?