public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "robert dot mance at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/37738] Fortran DW_TAG_common_block has incorrect placement/scope
Date: Tue, 18 Aug 2009 21:01:00 -0000 [thread overview]
Message-ID: <20090818210118.15613.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37738-12292@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from robert dot mance at intel dot com 2009-08-18 21:01 -------
(In reply to comment #4)
> Fixed.
Could you please tell me what version of gfortran this is fixed in? I'm
working the Intel Fortran compiler debug information at the moment regarding a
request to add DW_AT_common_inclusion to our output. Seems like gfortran has
actually decided to move in Intel's direction here. I'd like to see the output
that gfortran is now creating, and be able to run that version of gfortran
here.
Thanks.
Bob
--
robert dot mance at intel dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |robert dot mance at intel
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37738
next prev parent reply other threads:[~2009-08-18 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 15:18 [Bug debug/37738] New: " jan dot kratochvil at redhat dot com
2008-10-05 15:35 ` [Bug debug/37738] " jan dot kratochvil at redhat dot com
2008-10-06 15:12 ` jakub at gcc dot gnu dot org
2008-10-07 18:17 ` jakub at gcc dot gnu dot org
2008-12-08 22:24 ` mikael at gcc dot gnu dot org
2008-12-08 22:45 ` jakub at gcc dot gnu dot org
2009-08-18 21:01 ` robert dot mance at intel dot com [this message]
2009-08-18 21:17 ` jakub at gcc dot gnu dot org
2009-08-19 21:28 ` robert dot mance at intel dot com
2009-08-21 18:16 ` burnus 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=20090818210118.15613.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).