This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
- From: "Tobias dot Schlueter at physik dot uni-muenchen dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 May 2005 11:21:24 -0000
- Subject: [Bug fortran/21203] Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
- References: <20050425082043.21203.corsepiu@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de 2005-05-18 11:21 -------
Subject: Re: Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
Tobias dot Schlueter at physik dot uni-muenchen dot de wrote:
> ------- Additional Comments From Tobias dot Schlueter at physik dot uni-muenchen dot de 2005-05-14 15:25 -------
> Subject: Re: Segfault while compiling libgfortran/intrinsics/selected_int_kind.f90
>
> Quoting corsepiu at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org>:
>
>>As I tried to express before, I think this PR actually trips several bugs at
>>once.
>>
>>* A bug in error f95's handling, which probably causes the seg fault. The
>>compiler simply must not seg fault.
>
>
> Exactly, I assume this has to do with the fact that we're trying to initialize a
> zero-length parameter array, which is somewhat unusual, and thus probably not
> well-tested and buggy.
>
> I won't have access to my box, but if someone has a few spare minutes, I'd
> suggest he tries this code:
This did work correctly, so that's one possible problem less.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21203