public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32302] [4.2/4.3 Regression] Incorrect result with -O2
Date: Wed, 13 Jun 2007 05:09:00 -0000	[thread overview]
Message-ID: <20070613050904.9236.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32302-10129@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from kargl at gcc dot gnu dot org  2007-06-13 05:09 -------
(In reply to comment #3)
> (In reply to comment #2)
> > Until I know for sure, i am moving this back to the fortran component, it might
> > be a front end issuse still.
> > 
> Andrew,
> 
> I think that you are probably right - it looks like my patch for PR29786 is to
> blame, since it is the only thing to touch trans-common.c for a long time.  I
> am restricted to Cygwin and the moment and, with this dataflow problem, I
> cannot tell what is going on. In fact, the compiler will not even handle fixed
> form, for reasons that I do not see. 
> 
> Paul
> 

Paul,

If you access to a system, I can give you access to troutmask.
Send me your ssh public key, and you can play around on 
sgk@troutmask.  Yeah, it's trans-atlantic.


-- 


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


  parent reply	other threads:[~2007-06-13  5:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-12 13:40 [Bug fortran/32302] New: gfortran - incorrect result with -O3 dir at lanl dot gov
2007-06-12 15:04 ` [Bug middle-end/32302] [4.2, 4.3 Regression] Incorrect result with -O2 burnus at gcc dot gnu dot org
2007-06-12 15:09 ` [Bug fortran/32302] [4.2/4.3 " pinskia at gcc dot gnu dot org
2007-06-13  4:58 ` pault at gcc dot gnu dot org
2007-06-13  5:09 ` kargl at gcc dot gnu dot org [this message]
2007-06-13  9:02 ` pault at gcc dot gnu dot org
2007-06-13  9:05 ` pault at gcc dot gnu dot org
2007-06-13  9:31 ` pault at gcc dot gnu dot org
2007-06-13 12:26 ` pault at gcc dot gnu dot org
2007-06-13 13:39 ` dir at lanl dot gov
2007-06-13 15:00 ` pault at gcc dot gnu dot org
2007-06-14 12:00 ` patchapp at dberlin dot org
2007-06-14 13:04 ` pault at gcc dot gnu dot org
2007-06-14 13:05 ` [Bug fortran/32302] [4.2 " pault at gcc dot gnu dot org
2007-06-20  5:03 ` pault at gcc dot gnu dot org
2007-06-20  5:03 ` pault 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=20070613050904.9236.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).