This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: PR traget/24188 (-mcmodel=medium ICE)
- From: Tobias Schlüter <tobias dot schlueter at physik dot uni-muenchen dot de>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Richard Henderson <rth at redhat dot com>, Jan Hubicka <jh at suse dot cz>,gcc-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Fri, 04 Nov 2005 22:21:40 +0100
- Subject: Re: PR traget/24188 (-mcmodel=medium ICE)
- References: <20051104121104.GB23668@kam.mff.cuni.cz> <20051104204638.GA12817@redhat.com> <20051104205926.GK16034@devserv.devel.redhat.com>
Jakub Jelinek wrote:
> That's a Fortran string, not C. So empty string there is really 0 bytes
> long. Now the question is if it is really needed for the zero sized
> string literal to actually make it down to the rtl passes in the common
> cases.
> The empty string literal will appear in calls like:
> _gfortran_transfer_character ("", 0);
> or
> _gfortran_copy_string (10, &a, 0, "");
> etc.
> But I'm pretty certain none of those intrinsic routines would mind
> if NULL has been passed instead.
They are implemented using memcpy, strcat and the like. Is it valid to assume
that they will handle a NULL argument gracefully?
- Tobi