[Bug libfortran/43572] [4.5/4.6 Regression] FAIL: gfortran.dg/PR19872.f execution test; formatted read - wrong numbers
rguenth at gcc dot gnu dot org
gcc-bugzilla@gcc.gnu.org
Mon Apr 12 16:00:00 GMT 2010
------- Comment #13 from rguenth at gcc dot gnu dot org 2010-04-12 15:59 -------
(In reply to comment #12)
> A git bisect between the ranges suggested by Dave in Comment #6, gave me
> r149470 this as the first broken commit using a cross-compiler to
> arm-linux-gnueabi with qemu as the simulator .
>
> 2009-07-02 Richard Guenther <rguenther@suse.de>
>
> * tree-ssa-live.c (remove_unused_locals): Do not remove
> heap variables.
> * tree-ssa-structalias.c (handle_lhs_call): Delay setting
> of DECL_EXTERNAL for HEAP variables.
> (compute_points_to_sets): Set DECL_EXTERNAL for escaped
> HEAP variables. Do not adjust RESTRICT vars.
> (find_what_var_points_to): Nobody cares if something
> points to READONLY.
>
> My tools were configured as
>
> /home/ramrad01/cross-build/src/gcc-trunk/configure
> --target=arm-none-linux-gnueabi --enable-languages=c,c++,fortran
> --with-cpu=cortex-a8 --with-fpu=vfp3 --with-float=softfp
>
>
> In the middle of debugging further now to get to a reduced testcase given that
> the failure is a miscompile somewhere deep inside libgfortran.
The change shouldn't cause excessive changes, so if you compare
object files with and without that revision you should get at most
a single file I would guess. If the change reproduces with a cross
compiler (please provide configuration and compiler command-line details)
I can have a look. Note that there were later fixes to that patch
I believe (like the fix for PR40617). Unless you are sure you are
running exactly into the same problem bisection may lead you to false
intermediate broken libgfortran.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43572
More information about the Gcc-bugs
mailing list