This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/55174] [4.6 Regression] Segmentation fault with bad array reference
- From: "harper at msor dot vuw.ac.nz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 04 Nov 2012 20:41:10 +0000
- Subject: [Bug fortran/55174] [4.6 Regression] Segmentation fault with bad array reference
- Auto-submitted: auto-generated
- References: <bug-55174-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55174
--- Comment #3 from harper at msor dot vuw.ac.nz 2012-11-04 20:41:10 UTC ---
On Fri, 2 Nov 2012, janus at gcc dot gnu.org wrote:
> Date: Fri, 2 Nov 2012 10:54:50 +0000
> From: janus at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org>
> To: john.harper@vuw.ac.nz
> Subject: [Bug fortran/55174] [4.6 Regression] Segmentation fault with bad
> array reference
> Resent-Date: Fri, 2 Nov 2012 10:55:07 +0000
> Resent-From: <john.harper@vuw.ac.nz>
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55174
>
> janus at gcc dot gnu.org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Keywords| |ice-on-invalid-code
> Status|UNCONFIRMED |NEW
> Last reconfirmed| |2012-11-02
> CC| |janus at gcc dot gnu.org
> Summary|internal compiler error: |[4.6 Regression]
> |Segmentation fault with bad |Segmentation fault with bad
> |array reference |array reference
> Ever Confirmed|0 |1
>
> --- Comment #2 from janus at gcc dot gnu.org 2012-11-02 10:54:50 UTC ---
> (In reply to comment #1)
>> It looks like it has been fixed on trunk (aka 4.8.0).
>
> For me it also works with:
>
> gcc version 4.7.2 20120920 [gcc-4_7-branch revision 191568] (SUSE Linux)
>
> (while it fails with 4.7.0 and 4.6.0).
>
> Note: The 4.6 branch is still maintained, so we should consider fixing it
> there.
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
I have just tried gfortran 4.7.1 (x86_64-unknown-linux-gnu) and it
gave the internal compiler error with my program. So it seems that
4.7.0 and 4.7.1 both have the bug and 4.7.2 does not. Evidence:
miro[~]$ cat trybadstar.f90
implicit none
integer:: array(2)=(/42,666/)
print *, size(array(*))
end
miro[~]$ gf7 -v trybadstar.f90
Driving: /home/harperj1/gcc47/gf/bin/gfortran -v trybadstar.f90 -l
gfortran -l m -shared-libgcc
Using built-in specs.
COLLECT_GCC=/home/harperj1/gcc47/gf/bin/gfortran
COLLECT_LTO_WRAPPER=/home/harperj1/gcc47/gf/libexec/gcc/x86_64-unknown-linux-gnu/4.7.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /home/harperj1/gcc47/gcc-4.7.1/configure
--prefix=/home/harperj1/gcc47/gf --enable-languages=c,fortran
--disable-libada --with-local-prefix=/home/harperj1/gcc47
--with-gmp=/home/harperj1/gcc47
Thread model: posix
gcc version 4.7.1 (GCC)
COLLECT_GCC_OPTIONS='-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
/home/harperj1/gcc47/gf/libexec/gcc/x86_64-unknown-linux-gnu/4.7.1/f951
trybadstar.f90 -quiet -dumpbase trybadstar.f90 -mtune=generic
-march=x86-64 -auxbase trybadstar -version -fintrinsic-modules-path
/home/harperj1/gcc47/gf/lib/gcc/x86_64-unknown-linux-gnu/4.7.1/finclude -o
/tmp/ccFXH0I1.s
GNU Fortran (GCC) version 4.7.1 (x86_64-unknown-linux-gnu)
compiled by GNU C version 4.7.1, GMP version 4.3.1, MPFR version
2.4.1, MPC version 0.8
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU Fortran (GCC) version 4.7.1 (x86_64-unknown-linux-gnu)
compiled by GNU C version 4.7.1, GMP version 4.3.1, MPFR version
2.4.1, MPC version 0.8
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
f951: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
miro[~]$
-- John Harper, School of Mathematics Statistics and Operations Research
Victoria University, PO Box 600, Wellington 6140, New Zealand
e-mail john.harper@vuw.ac.nz phone (+64)(4)463 5276 fax (+64)(4)463 5045