From: Jim Blandy <jimb@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sources.redhat.com, ezannoni@redhat.com
Subject: Re: [RFA/dwarf] Eliminate dwarf2_tmp_obstack
Date: Mon, 19 Apr 2004 12:42:00 -0000 [thread overview]
Message-ID: <vt2vfjwwj1b.fsf@zenia.home> (raw)
In-Reply-To: <uisfwlaqs.fsf@elta.co.il>
Eli Zaretskii <eliz@elta.co.il> writes:
> > Date: Sun, 18 Apr 2004 23:17:44 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > dwarf2_tmp_obstack serves as a general purpose dumping ground. After my
> > previous patches, there are only two things left on it: the linked list we
> > use to fudge GCC 2.95 line number tables (some day soon I think this hack
> > should go away; it was primarily for the benefit of the testsuite, and was
> > fixed at least as of GCC 3.1)
>
> FWIW, I don't think it's time to dump support for GCC 2.95: it is
> still in wide use as the system compiler on many GNU platforms.
I think you are right about the prevalence of GCC 2.95. Michael
Chastain has made the same sorts of comments.
But dropping the kludge in question is not the same as dropping GCC
2.95 support. The kludge is a fix for a specific GCC 2.95 bug, and if
I remember right, GDB had been in widespread use with that compiler
for several releases before the bug got fixed. I think GCC 2.95
defaulted to STABS on the i386 anyway. (I apologize for being too
lazy to search the archives to verify all this.)
next prev parent reply other threads:[~2004-04-19 12:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 3:17 Daniel Jacobowitz
2004-04-19 5:55 ` Eli Zaretskii
2004-04-19 12:42 ` Jim Blandy [this message]
2004-04-19 13:18 ` Daniel Jacobowitz
2004-04-19 12:42 ` Jim Blandy
2004-04-19 13:21 ` Daniel Jacobowitz
2004-04-19 18:15 ` Jim Blandy
2004-04-19 23:30 ` Daniel Jacobowitz
2004-04-19 18:25 Michael Elizabeth Chastain
2004-04-19 18:27 ` Daniel Jacobowitz
2004-04-19 18:33 Michael Elizabeth Chastain
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=vt2vfjwwj1b.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.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