public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/23057] Fortran common blocks are not described with DW_TAG_common_block Date: Wed, 03 Aug 2005 20:21:00 -0000 [thread overview] Message-ID: <20050803202127.15384.qmail@sourceware.org> (raw) In-Reply-To: <20050725054001.23057.woodzltc@sources.redhat.com> ------- Additional Comments From howarth at nitro dot med dot uc dot edu 2005-08-03 20:21 ------- Andrew, Do you think you might be interested in tackling the implementation of the DW_TAG_common_block tag if we could get HJ Lu and/or Jakub Jelinek to provide technical assistance? Having the ability to debug COMMON blocks in gfortran would be quite helpful for programs like xplor-nih that heavily use them. Jack -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23057
next prev parent reply other threads:[~2005-08-03 20:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-25 5:41 [Bug fortran/23057] New: Wrong DWARF output for Fortran common block woodzltc at sources dot redhat dot com 2005-07-25 5:48 ` [Bug fortran/23057] " pinskia at gcc dot gnu dot org 2005-07-25 7:35 ` [Bug fortran/23057] Fortran common blocks are not described with DW_TAG_common_block pinskia at gcc dot gnu dot org 2005-08-03 20:21 ` howarth at nitro dot med dot uc dot edu [this message] 2005-08-03 20:25 ` pinskia at gcc dot gnu dot org [not found] <bug-23057-10906@http.gcc.gnu.org/bugzilla/> 2007-10-28 14:24 ` fxcoudert at gcc dot gnu dot org 2007-11-18 14:56 ` george at gly dot bris dot ac dot uk 2008-04-02 8:08 ` george at gcc dot gnu dot org 2008-08-29 18:43 ` jakub at gcc dot gnu dot org 2008-08-29 18:48 ` jakub 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=20050803202127.15384.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: linkBe 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).