This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: internal compiler error: Segmentation fault
- From: FX <fxcoudert at gmail dot com>
- To: "J. Finch" <finchlady888 at hotmail dot com>
- Cc: "fortran at gcc dot gnu dot org" <fortran at gcc dot gnu dot org>, "GCC Development" <gcc at gcc dot gnu dot org>, mingw-w64-public at lists dot sourceforge dot net
- Date: Wed, 9 Jan 2008 15:09:25 +0000
- Subject: Re: internal compiler error: Segmentation fault
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=keHfKeXAhv0Ywde2ZqFqhX3+3+fk7kaUsovzpVmUIm8=; b=Oos7sXBouvAOFcRYURB/B8qm/XJKmCzP67GrD8splhnBiCObYlLAds4sCdaki6M1wDciUfzS/53VUY2iAwHhS8CBUzEsZeVkb4aPk4exINo+95dI5dpP3nxlxEjrHUm8kGzCSvLrkOI557/g3TnrWFsPpkA34rPBraAJv4+eTmE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ioGkka1lchIroMGgA20b9NDblR1ds8Os5C1y8R4cJhAcQr+AlrfvaXkorCgw/IZXCtL3A/sktIf+L9BS3oKf91QJNyAYatsz2PEckSn2jW2P86YnPH1XBfCictQm4tNfXTlGWLopUuw/b0v1StIHuyEnkpO/LC+FgJla1yF3v7k=
- References: <19c433eb0801090519l676a7645u162dc18760e99cc9@mail.gmail.com> <BAY127-W419B706D2D2ACAC13608CE8D490@phx.gbl>
[for mingw-w64-public@... and gcc@... readers, seeshort thread
starting at http://gcc.gnu.org/ml/fortran/2008-01/msg00103.html]
> Gcc gets the similar problem. It only works without optimization. It seems not a problem with gfortran.
OK, then it'd be more appropriate to ask the mingw mailing-list or the
generic gcc@gcc.gnu.org list.
> GMP version is 4.2.2, and has been modified for x86_64. The original 4.2.2 does not support x86_64-pc-mingw32.
Does GMP pass tests? Have you built it with extra checking enabled? I
don't suspect what you're seeing is a GMP problem, but you can never
be too sure.
> I do not have gdb for windows for the time being.
That's why I gave you a download link for MS debuggers (I don't think
gdb is supported on x86_64-mingw32). I'm not sure much can be done
without a debugger.
FX