> The newly built gfortran must be stomping on memory. I've found that
> attached patch allows gfortran to still function. Could someone who
> sees this problem try bootstrapping gfortran with the patch?
gfortran bootstrapped OK with this patch on ppc64 r126353.
Thanks,
Revital
> The newly built gfortran must be stomping on memory. I've found that
> attached patch allows gfortran to still function. Could someone who
> sees this problem try bootstrapping gfortran with the patch?
I will try it.
Revital
Dorit sent me a copy of the libgfortran/config.log on
her failing system. In looking through the log, I've
found (note, I've paths to ABC, XYZ for shortness):
configure:11335: checking if ABC/./gcc/gfortran -BABC/./gcc/ -BXYZ/bin/
-BXYZ/lib/ -isystem XYZ/include -isystem XYZ/sys-include suppo
On Sat, Jul 07, 2007 at 12:45:59PM +0200, Bernhard Fischer wrote:
> On Fri, Jul 06, 2007 at 10:08:44AM -0700, Steve Kargl wrote:
> >On Fri, Jul 06, 2007 at 12:07:43PM -0400, Diego Novillo wrote:
>
> >Dorit has isolated the problem to the ISO C Binding import. See
> >for example
> >
> >http://gcc.
On Fri, Jul 06, 2007 at 10:08:44AM -0700, Steve Kargl wrote:
>On Fri, Jul 06, 2007 at 12:07:43PM -0400, Diego Novillo wrote:
>Dorit has isolated the problem to the ISO C Binding import. See
>for example
>
>http://gcc.gnu.org/ml/gcc/2007-07/msg00133.html
>
>AFAIK, ppc64 is the only target that is
On 7/6/07 3:31 PM, Brooks Moses wrote:
> Hmm. Looking at that, I suspect that the relevant file is actually the
> "selected_int_kind.inc" one that it includes. Can you post that as well?
Attached.
integer, parameter :: c = 5
type (int_info), parameter :: int_infos(c) = (/ &
int_info (1,
Diego Novillo wrote:
On 7/6/07 1:14 PM, Steve Kargl wrote:
One other thing. Can you post the contents of
perf/sbox/gcc/local.ppc64/src/libgfortran/intrinsics/selected_int_kind.f90
This is file is autogenerated. If it's mangled you'll get the
failure.
Attached. The failure still exists wit
On 7/6/07 1:14 PM, Steve Kargl wrote:
> One other thing. Can you post the contents of
>
> perf/sbox/gcc/local.ppc64/src/libgfortran/intrinsics/selected_int_kind.f90
>
> This is file is autogenerated. If it's mangled you'll get the
> failure.
Attached. The failure still exists with the latest
On 7/6/07 1:14 PM, Steve Kargl wrote:
> perf/sbox/gcc/local.ppc64/src/libgfortran/intrinsics/selected_int_kind.f90
>
> This is file is autogenerated. If it's mangled you'll get the
> failure.
Sure, but I've lost the file. I'm trying to bootstrap from scratch with
the latest version of GMP/MPFR
On Fri, Jul 06, 2007 at 10:08:44AM -0700, Steve Kargl wrote:
>
> Dorit has isolated the problem to the ISO C Binding import. See
> for example
>
> http://gcc.gnu.org/ml/gcc/2007-07/msg00133.html
>
> AFAIK, ppc64 is the only target that is failing. I'll send you
> my public key later today (I
On Fri, Jul 06, 2007 at 12:07:43PM -0400, Diego Novillo wrote:
> On 7/6/07 11:48 AM, FX Coudert wrote:
>
> > Depends what is your current version,
>
> $ rpm -q gmp
> gmp-4.1.4-12
>
>
> > I guess. Can you get us a backtrace?
>
> Well, it seems to be a mis-compilation of f951. The stage3 f951 b
On 7/6/07 11:48 AM, FX Coudert wrote:
> Depends what is your current version,
$ rpm -q gmp
gmp-4.1.4-12
> I guess. Can you get us a backtrace?
Well, it seems to be a mis-compilation of f951. The stage3 f951 binary
dies trying to fold an INDIRECT_REF with a NULL type (suspicious). The
stage1
Starting 2007-07-02 my daily ppc64 tester has failed bootstrap with
a SEGV in libgfortran:
libtool: compile: /home/dnovillo/perf/sbox/gcc/local.ppc64/bld/./
gcc/gfortran -B/home/dnovillo/perf/sbox/gcc/local.ppc64/bld/./gcc/ -
B/home/dnovillo/perf/sbox/gcc/local.ppc64/inst/powerpc64-unknown-
Starting 2007-07-02 my daily ppc64 tester has failed bootstrap with a SEGV in
libgfortran:
libtool: compile: /home/dnovillo/perf/sbox/gcc/local.ppc64/bld/./gcc/gfortran
-B/home/dnovillo/perf/sbox/gcc/local.ppc64/bld/./gcc/
-B/home/dnovillo/perf/sbox/gcc/local.ppc64/inst/powerpc64-unknown-linu
14 matches
Mail list logo
