public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reuter at mail dot desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/40413] Internal error in connection with optimization and allocatable objects
Date: Thu, 11 Jun 2009 19:31:00 -0000	[thread overview]
Message-ID: <20090611193150.11133.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40413-15192@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from reuter at mail dot desy dot de  2009-06-11 19:31 -------
Subject: Re:  Internal error in connection with optimization
 and allocatable objects

On Thu, 11 Jun 2009, dominiq at lps dot ens dot fr wrote:


Thanks for the explanations. I actually cannot change the priority,
only the assignee or a specifically empowered user can change the status.

>
>
> ------- 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
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>

------------------------------------
Juergen Reuter
Albrecht-Ludwigs-Universitaet Freiburg
Physikalisches Institut
Hermann-Herder-Str. 3
79104 Freiburg, GERMANY
Tel.: +49-761-203-8407
Skype: jr_reuter
------------------------------------


-- 


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


  parent reply	other threads:[~2009-06-11 19:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 10:01 [Bug fortran/40413] New: " juergen dot reuter at desy dot de
2009-06-11 10:34 ` [Bug fortran/40413] " dominiq at lps dot ens dot fr
2009-06-11 14:55 ` reuter at mail dot desy dot de
2009-06-11 15:23 ` dominiq at lps dot ens dot fr
2009-06-11 19:31 ` reuter at mail dot desy dot de [this message]
2009-06-11 21:47 ` dominiq at lps dot ens dot fr
2009-06-12  5:21 ` [Bug fortran/40413] [4.5 Regression] " pault at gcc dot gnu dot org
2009-06-13 14:08 ` [Bug tree-optimization/40413] " rguenth at gcc dot gnu dot org
2009-06-13 15:52 ` pault at gcc dot gnu dot org
2009-06-14  1:30 ` jamborm at gcc dot gnu dot org
2009-06-15  9:07 ` jamborm at gcc dot gnu dot org
2009-06-16  9:54 ` jamborm at gcc dot gnu dot org
2009-06-16 10:12 ` jamborm at gcc dot gnu dot org
2009-06-16 10:24 ` jamborm at gcc dot gnu dot 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=20090611193150.11133.qmail@sourceware.org \
    --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).