public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pepalogik at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52621] New: ICE when compiling Fortran77 code with optimization
Date: Mon, 19 Mar 2012 16:13:00 -0000 [thread overview]
Message-ID: <bug-52621-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52621
Bug #: 52621
Summary: ICE when compiling Fortran77 code with optimization
Classification: Unclassified
Product: gcc
Version: 4.6.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: pepalogik@seznam.cz
Created attachment 26920
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26920
Library source producing the ICE
I am compiling an old Fortran 77 code on Windows XP. I have fixed this code to
make it basically work in both FTN95 (Silverfrost) and gfortran compilers. But
when I try to make a highly optimized build with gfortran, I get an ICE.
Compiler version:
C:\MinGW\bin>gfortran.exe -v
Using built-in specs.
COLLECT_GCC=gfortran.exe
COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.6.1/lto-wrapper.exe
Target: mingw32
Configured with: ../gcc-4.6.1/configure
--enable-languages=c,c++,fortran,objc,ob
j-c++ --disable-sjlj-exceptions --with-dwarf2 --enable-shared --enable-libgomp
-
-disable-win32-registry --enable-libstdcxx-debug
--enable-version-specific-runti
me-libs --build=mingw32 --prefix=/mingw
Thread model: win32
gcc version 4.6.1 (GCC)
Command:
gfortran.exe -std=legacy -march=native -mfpmath=sse -m3dnow -mmmx -msse -msse2
-msse3 -O3 -Wall -c D:\Jenda\cbp\SATLEED\LEEDSATL_SB\leedsatl_sb.f -o
obj\Release\leedsatl_sb.o
CPU: AMD Athlon x2, see
<http://www.cpu-world.com/CPUs/K8/AMD-Athlon%20X2%204850e%20-%20ADH4850IAA5DO%20(ADH4850DOBOX).html>
Important: The ICE is gone if I decrease the optimization level to -O2 or
exclude the machine specific options (from -march to -msse3).
The code and output are attached.
Copyright note: The code comes from
<http://www.ap.cityu.edu.hk/personal-website/Van-Hove_files/leed/leedpack.html>
and I am actually not allowed to distribute it.
next reply other threads:[~2012-03-19 16:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 16:13 pepalogik at seznam dot cz [this message]
2012-03-19 16:17 ` [Bug fortran/52621] " pepalogik at seznam dot cz
2012-03-20 8:42 ` burnus at gcc dot gnu.org
2012-03-21 12:45 ` pepalogik at seznam dot cz
2012-03-21 13:22 ` dominiq at lps dot ens.fr
2012-03-21 13:33 ` [Bug middle-end/52621] ICE with -O3 -march=opteron in initialize_matrix_A, at tree-data-ref.c:1964 burnus at gcc dot gnu.org
2012-03-21 13:52 ` [Bug middle-end/52621] [4.6/4.7/4.8 Regression] " dominiq at lps dot ens.fr
2012-03-21 14:21 ` dominiq at lps dot ens.fr
2012-03-21 14:27 ` dominiq at lps dot ens.fr
2012-04-05 10:52 ` rguenth at gcc dot gnu.org
2012-04-05 11:27 ` rguenth at gcc dot gnu.org
2012-04-11 12:18 ` rguenth at gcc dot gnu.org
2012-04-11 14:05 ` rguenth at gcc dot gnu.org
2012-04-11 14:21 ` [Bug middle-end/52621] [4.6/4.7 " rguenth at gcc dot gnu.org
2012-04-13 13:00 ` rguenth at gcc dot gnu.org
2012-07-06 9:20 ` rguenth at gcc dot gnu.org
2012-07-06 9:27 ` [Bug middle-end/52621] [4.6 " rguenth at gcc dot gnu.org
2012-07-17 22:56 ` danglin at gcc dot gnu.org
2013-04-12 16:27 ` jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-52621-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).