This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/40413] Internal error in connection with optimization and allocatable objects
- From: "dominiq at lps dot ens dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Jun 2009 15:23:22 -0000
- Subject: [Bug fortran/40413] Internal error in connection with optimization and allocatable objects
- References: <bug-40413-15192@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from dominiq at lps dot ens dot fr 2009-06-11 15:23 -------
> I'm not so much of an export in the terminology. What exactly does
> regression mean?
It means that a code worked at revision n (here 4.4.0) and no longer at
revision n+1 (here 4.5.0). This means that either something has been broken by
some change or a bug has been exposed by it. Since changes are supposed to
improve any piece of code, regressions have in general a higher priority than
other bugs, so it is important to mark them in the subject line (look at
http://gcc.gnu.org/ml/gcc-bugs/2009-06/ for examples). Since I don't have the
rights to change the subject line, you have to do it yourself or wait for some
maintainer to do it.
> The option -m64 does work. What exactly does it do?
It forces the compilation in "64 bit mode" while the default in Darwin is 32
bit. I don't know the detail of the differences besides the fact that the
addresses are coded on 64 bits instead of 32 and in general the code runs
faster (~10 to 20%) with -m64.
Note that I provided the information in the hope to help those who will fix the
bug, meanwhile you can use -m64 as a workaround.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40413