--- Comment #29 from fxcoudert at gcc dot gnu dot org 2006-09-25 09:19
---
Subject: Bug 21203
Author: fxcoudert
Date: Mon Sep 25 09:19:36 2006
New Revision: 117191
URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=117191
Log:
PR fortran/21203
* error.c (show_loci):
--- Comment #28 from tobi at gcc dot gnu dot org 2006-02-12 18:47 ---
Ralf, this patch should fix the segfault, it shouldn't give you a working
compiler, though.
Index: error.c
===
--- error.c (revision 110873)
+++
--- 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
--- Additional Comments From joel at oarcorp dot com 2005-05-16 14:00
---
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
corsepiu at gcc dot gnu dot org wrote:
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-14
08:33
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-16
14:05 ---
(In reply to comment #24)
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
corsepiu at gcc dot gnu dot org wrote:
Joel, do you recall the target in RTEMS which
corsepiu at gcc dot gnu dot org wrote:
Joel, do you recall the target in RTEMS which has 4-byte floats only?
(We recently had an issue with it floating point context sizes related to it?
IIRC, it had been a powerpc variant and we were forced to drop it because GCC
doesn't support it.
BTW1: IFAIK,
--- Additional Comments From toon at moene dot indiv dot nluug dot nl
2005-05-15 18:49 ---
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
corsepiu at gcc dot gnu dot org wrote:
Joel, do you recall the target in RTEMS which has 4-byte floats only?
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-14
06:30 ---
(In reply to comment #11)
Ralf, it looks like no working integer type is found when building the
compiler.
The h8300 is special wrt. integer types:
From a test script of mine:
...
checking for
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-14
07:00 ---
(In reply to comment #13)
I'll try again this weekend with the version of GMP on the laptop
and update GMP if it still fails. If you go to the GMP home page
there is a VERY big warning about problems
On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
* f95 disqualifies ifselves from several embedded targets, if it can
not be
built/used on targets not supporting REAL8. IIRC, there even exist
variants of
major _targets_ (IIRC, powerpc, m68k) which do not support REAL8.
IMO,
--- Additional Comments From pinskia at physics dot uc dot edu 2005-05-14
07:04 ---
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
* f95 disqualifies ifselves from several
On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
* f95 disqualifies ifselves from several embedded targets, if it can
not be
built/used on targets not supporting REAL8. IIRC, there even exist
variants of
major _targets_ (IIRC, powerpc, m68k) which do not support REAL8.
IMO,
--- Additional Comments From pinskia at physics dot uc dot edu 2005-05-14
07:08 ---
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
* f95 disqualifies ifselves from several
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-14
08:14 ---
(In reply to comment #17)
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
* f95
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-14
08:33 ---
(In reply to comment #16)
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
On May 14, 2005, at 3:00 AM, corsepiu at gcc dot gnu dot org wrote:
* f95
--- 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 [EMAIL PROTECTED]:
As I tried to express before, I
--- Additional Comments From sgk at troutmask dot apl dot washington dot
edu 2005-05-14 15:57 ---
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
On Sat, May 14, 2005 at 03:25:17PM -, Tobias dot Schlueter at physik dot
uni-muenchen dot de
--- Additional Comments From sgk at troutmask dot apl dot washington dot
edu 2005-05-14 16:06 ---
Subject: Re: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
On Sat, May 14, 2005 at 08:14:48AM -, corsepiu at gcc dot gnu dot org wrote:
Free free to hang
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-15
03:55 ---
(In reply to comment #20)
I think, I have isolated the bug:
BUG #1:
During bootstrap, libgfortran/Makefile tries to generate selected_int_kind.inc:
selected_int_kind.inc: $(srcdir)/mk-sik-inc.sh
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-13
07:56 ---
Created an attachment (id=8884)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8884action=view)
selected_int_kind.f90
As requested by Tobi, the selected_int_kind.f90 building h8300-rtems4.7
gcc-4.0.1
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-05-13
07:59 ---
Created an attachment (id=8885)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8885action=view)
selected_int_kind.inc
Sorry, wrong file. This is the *.inc, Tobi requested.
--
--- Additional Comments From kargl at gcc dot gnu dot org 2005-05-13 18:48
---
(In reply to comment #9)
Created an attachment (id=8885)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8885action=view)
selected_int_kind.inc
Sorry, wrong file. This is the *.inc, Tobi requested.
I
--- Additional Comments From tobi at gcc dot gnu dot org 2005-05-13 19:25
---
Steve, are you saying that you're seeing the same failure on a Pentium 4
machine? This would be weird because ...
Ralf, it looks like no working integer type is found when building the
compiler.
I'm out
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-05-13
20:34 ---
(In reply to comment #11)
Steve, are you saying that you're seeing the same failure on a Pentium 4
machine? This would be weird because ...
Steve, I have heard that there are some GMP with bugs which
--- Additional Comments From kargl at gcc dot gnu dot org 2005-05-13 21:30
---
Tobi and Andrew, Yes, I see this exact failure on FreeBSD with
a pentium 4 M processor. I spent a few days hacking on Makefiles
to turn on/off different compiler options and could never resolve
the issues.
--- Additional Comments From tobi at gcc dot gnu dot org 2005-05-11 23:12
---
Can you attach the selected_int_kind.inc which is generated in the library build
directory? Probably the problem can be reproduced on other platforms when
trying to compile selected_int_kind.f90.
--
--- Additional Comments From ericw at evcohs dot com 2005-05-05 17:25
---
(In reply to comment #2)
Bootstrapping avr-rtems w/ f95 enabled trips a similar or may-be the same bug
(also a target which probably doesn't provide REAL 8).
As a side note, it is known that Fortran does not
--- Additional Comments From ert at roe dot ac dot uk 2005-05-01 14:44
---
Subject: New: Segfault while compiling
libgfortran/intrinsics/selected_int_kind.f90
I get the same error compiling gcc-4.0.0 on an Opteron with Debian-3
(32-bit, glibc-2.2.5, 2.4.26 kernel)
The failure
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-25
13:30 ---
Hmm.
--
What|Removed |Added
Keywords||build,
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-04-25
14:33 ---
(In reply to comment #1)
Hmm.
The origin of this issue seems to be f951's check's for REAL 8 (kind=8).
The h8300 doesn't seem to provide this type and thereby seems to trigger a bug
in f951's error
--- Additional Comments From kargl at gcc dot gnu dot org 2005-04-25 16:38
---
(In reply to comment #2)
The origin of this issue seems to be f951's check's for REAL 8 (kind=8).
The h8300 doesn't seem to provide this type and thereby seems to trigger a bug
in f951's error handling.
--- Additional Comments From corsepiu at gcc dot gnu dot org 2005-04-25
17:14 ---
(In reply to comment #3)
(In reply to comment #2)
The origin of this issue seems to be f951's check's for REAL 8 (kind=8).
The h8300 doesn't seem to provide this type and thereby seems to trigger
32 matches
Mail list logo
