From: Jim Blandy <jimb@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/dwarf-1/comments] update dwarf-1 status info
Date: Thu, 29 Apr 2004 16:09:00 -0000 [thread overview]
Message-ID: <vt2wu3yojmr.fsf@zenia.home> (raw)
In-Reply-To: <20040424064222.4A2914B104@berman.michael-chastain.com>
mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:
> This patch updates the dwarfread.c info on the state of dwarf-1.
>
> . gcc 3.4.0 has removed support for dwarf-1 (cheer!)
> . i found another user bug report from 2003-07-25 about diab 4.4b.
> . diab 5.0.1, released 2002-07-31, supports both dwarf-1 and dwarf-2
> . absoft fortran 90/95, released 2001, supports both dwarf-1 and dwarf-2
>
> Testing: this is a comment-only patch. I built gdb and that's it.
>
> I plan to propose the obsoletion of dwarf-1 soon, but that proposal
> is separate from this patch. This patch just provides current
> information, without any opinions or policy judgements.
>
> Okay to commit?
Sure thing, please do.
prev parent reply other threads:[~2004-04-29 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 6:42 Michael Elizabeth Chastain
2004-04-29 16:09 ` Jim Blandy [this message]
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=vt2wu3yojmr.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
/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