public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46327] type field access by . (instead of %) unsupported
Date: Sat, 06 Nov 2010 06:20:00 -0000	[thread overview]
Message-ID: <bug-46327-4-49A6PqEjbc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46327-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2010-11-06 06:20:06 UTC ---
On Sat, Nov 06, 2010 at 05:01:45AM +0000, jan.kratochvil at redhat dot com
wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46327
> 
> --- Comment #2 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2010-11-06 05:01:35 UTC ---
> (In reply to comment #1)
> > Hopefully, this will never be supported in gfortran.
> 
> The problem is users continue to use iFort and I have to continue supporting it
> in GDB as they sources work fine in iFort.  It is fine if an explicit gfortran
> compilation option is required.
> 

Their source may work fine with ifort, but it is
not standard conforming Fortran.  If they need
to debug their code, then they should use Intel's
debugger.  Their code will not compile with
gfortran, so trying to debug gfortran compiled
Fortran code should not be an issue with gdb.


  parent reply	other threads:[~2010-11-06  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06  4:41 [Bug fortran/46327] New: " jan.kratochvil at redhat dot com
2010-11-06  4:49 ` [Bug fortran/46327] " kargl at gcc dot gnu.org
2010-11-06  5:01 ` jan.kratochvil at redhat dot com
2010-11-06  6:20 ` sgk at troutmask dot apl.washington.edu [this message]
2010-11-06  6:50 ` sgk at troutmask dot apl.washington.edu
2010-11-06  7:18 ` jan.kratochvil at redhat dot com
2010-11-06  9:21 ` steven at gcc dot gnu.org
2010-11-06  9:25 ` dominiq at lps dot ens.fr

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-46327-4-49A6PqEjbc@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).