This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/28788] [gfortran: 4.1, 4.2 regression] ICE on valid code



------- Comment #8 from paulthomas2 at wanadoo dot fr  2006-08-25 13:25 -------
Subject: Re:  [gfortran: 4.1, 4.2 regression] ICE on valid
 code

martin,

>------- Comment #7 from martin at mpa-garching dot mpg dot de  2006-08-25 12:57 -------
>Hi Paul,
>
>sorry for the late reply, I was away for a few days.
>I compiled the most recent gcc sources, and there still appears to be some
>bad memory access inside gfortran, which causes the compiler to sometimes
>work fine sometimes, sometimes give incorrect errors, and sometimes segfault :(
>
>I have a testcase where gfortran works fine, but reports a bogus error when I
>add
>"-I." to the command line.
>
>I fear the best way to locate this is to use valgrind or something similar on
>the compiler, and I don't manage to produce a small (single-file) testcase at
>the moment. Any ideas what I could do?
>
>
>  
>
Perhaps you can let me have an idea of the kind of code that is doing 
this?  Is this a continuation of the derived type problem or did it 
exist prior to the patch of a week back?

A good starting point is to use gdb on 
$yourgccpath/libexec/gcc/i*/4.2.0/f951 ;
Then run "command line"

Best regards

Paul


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28788


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]