public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jb at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24546] [meta-bug] gfortran debugging problems
Date: Mon, 21 Nov 2005 16:01:00 -0000 [thread overview]
Message-ID: <20051121160151.28882.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24546-10391@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from jb at gcc dot gnu dot org 2005-11-21 16:01 -------
Just as a general note, the deadline for dwarf3 comments is Dec 1, 2005. So if
anyone with some clue about how to improve support for debugging fortran has
some good suggestions that would require changes in the debug format, now is
the time to send them.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24546
next prev parent reply other threads:[~2005-11-21 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 18:17 [Bug fortran/24546] New: " tkoenig at gcc dot gnu dot org
2005-10-27 23:13 ` [Bug fortran/24546] " pinskia at gcc dot gnu dot org
2005-10-27 23:32 ` pinskia at gcc dot gnu dot org
2005-10-28 4:51 ` woodzltc at sources dot redhat dot com
2005-11-10 4:04 ` pinskia at gcc dot gnu dot org
2005-11-11 9:18 ` woodzltc at sources dot redhat dot com
2005-11-21 16:01 ` jb at gcc dot gnu dot org [this message]
2005-11-22 3:49 ` woodzltc at sources dot redhat dot com
2007-03-03 12:06 ` fxcoudert at gcc dot gnu dot org
2007-05-20 21:20 ` tkoenig at gcc dot gnu dot org
[not found] <bug-24546-4@http.gcc.gnu.org/bugzilla/>
2013-06-25 9:05 ` dominiq at lps dot ens.fr
2013-06-25 9:13 ` dominiq at lps dot ens.fr
2013-12-05 0:46 ` burnus at gcc dot gnu.org
2015-08-30 21:45 ` dominiq at lps dot ens.fr
2015-10-29 13:37 ` dominiq at lps dot ens.fr
2024-03-20 21:54 ` anlauf at gcc dot gnu.org
2024-03-21 18:35 ` anlauf at gcc dot gnu.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=20051121160151.28882.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).