public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@redhat.com>
To: gcc-gnats@gcc.gnu.org
Subject: web/6376: missing dwarf3 doc link
Date: Fri, 19 Apr 2002 09:06:00 -0000 [thread overview]
Message-ID: <200204191601.g3JG1IU26532@tonopah.toronto.redhat.com> (raw)
>Number: 6376
>Category: web
>Synopsis: missing dwarf3 doc link
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: gerald
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Fri Apr 19 09:06:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:
>Release: 3.2 20020307 (experimental)
>Organization:
>Environment:
System: Linux tonopah.toronto.redhat.com 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown
Architecture: i686
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure
>Description:
On the further readings page
http://gcc.gnu.org/readings.html
near the bottom, there are links to DWARF2 documentation which are
now obsolete. We should have in addition (or instead) a link to the
current DWARF3 documentation.
http://www.eagercon.com/dwarf/dwarf3std.htm
Putting this link before the DWARF 2.1 drafts link, and calling it
DWARF 3 drafts would be good.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-19 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 9:06 Jim Wilson [this message]
2002-04-20 5:57 rodrigc
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=200204191601.g3JG1IU26532@tonopah.toronto.redhat.com \
--to=wilson@redhat.com \
--cc=gcc-gnats@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).