This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
derived-type bug, is it new?
- From: François-Xavier Coudert <fxcoudert at gmail dot com>
- To: gfortran <fortran at gcc dot gnu dot org>
- Date: Mon, 6 Feb 2006 14:43:00 +0100
- Subject: derived-type bug, is it new?
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GEiOua7h9tTXJMjvVpBS3U1W43uPUFS0b0CjOUx9kLT7QxAE81oW3mSoQhbun12qIuiQlLDXQ+ac6LO2f4Ryr71T+yEINzb+1DSC5ZA93dei22v+LNCYO+RJmepQVQjghcX5BB9bG9SmEBhoimU6whH/XTv476LzXTSM2A9qkV0=
With gfortran 4.2.0 20060206 on i686-linux, I get the following:
$ cat a.f90
TYPE T
CHARACTER(LEN=80) :: S(1)
END TYPE T
TYPE(T), POINTER :: TT
PRINT *, LEN(TT % S)
END
$ gfortran -c a.f90
a.f90: In function 'MAIN__':
a.f90:1: internal compiler error: Segmentation fault
Does that ring a bell to someone, or should I file it? I'm sorry but I
don't have access to a debug-enabled tree right now, so I can't search
bugzilla for the f951 backtrace...
FX