Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dan@dberlin.org>
Cc: Petr Sorfa <petrs@caldera.com>, gdb@sources.redhat.com
Subject: Re: Upcoming DWARF 3 and FORTRAN95 patches for 5.1.1 or 5.2?
Date: Thu, 17 Jan 2002 15:10:00 -0000	[thread overview]
Message-ID: <20020117180959.A2987@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0201171804040.20234-100000@dberlin.org>

On Thu, Jan 17, 2002 at 06:06:11PM -0500, Daniel Berlin wrote:
> On Thu, 17 Jan 2002, Daniel Jacobowitz wrote:
> 
> > On Thu, Jan 17, 2002 at 05:03:14PM -0500, Petr Sorfa wrote:
> > > Hi,
> > > 
> > > I'll be releasing several patches soon, starting with some DWARF III
> > > support next week (I hope) and FORTRAN95 starting in March.
> > >  
> > > Just curious as to what timeline these patches will fit in (once they
> > > are accepted.) The DWARF III I see making the 5.1.1 tree, but the
> > > FORTRAN95 patches?
> > 
> > Nothing's going to make 5.1.1.  It's far too late; it'll be released in
> > a week, if I understood Andrew correctly.
> > 
> > Can you be more specific - what parts of DWARF3?  I've been working on
> > the dwarf2 reader in my spare time, and I'm willing to bet you'll
> > clobber all of those patches, so it would be nice if you fixed what I
> > was working on :P
> 
> I would imagine, based on reading some stuff on Intel's web site (that 
> said they were having caldera modify gdb for them to support their 
> compiler's debug output), that  he's adding the pieces needed to support 
> Intel's C++ Compiler for Linux.
> 
> I have a list of what that outputs that gdb doesn't currently supports 
> somewhere, but it might be easier for you to just look yourself, as it 
> would take me a while to find it.

If you have a chance to find it, I'd appreciate it.  Otherwise I'll
wait for Petr; I'm swamped.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-01-17 23:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-17 14:08 Petr Sorfa
2002-01-17 14:56 ` Daniel Jacobowitz
2002-01-17 15:07   ` Daniel Berlin
2002-01-17 15:10     ` Daniel Jacobowitz [this message]
2002-01-17 15:46       ` Petr Sorfa
2002-01-17 16:12         ` Daniel Berlin
2002-01-18  7:08           ` Petr Sorfa
2002-01-18  8:09             ` Petr Sorfa
2002-01-18 12:09               ` Daniel Berlin
2002-01-18 11:46                 ` Petr Sorfa
2002-01-18 12:10                   ` Daniel Berlin
2002-01-23 15:41                     ` Jim Blandy
2002-01-23 16:18                       ` Daniel Berlin
2002-01-23 16:36                         ` Andrew Cagney
2002-01-23 17:10                           ` Daniel Berlin
2002-01-23 16:38                       ` Daniel Jacobowitz
2002-01-23 17:19                         ` Daniel Berlin
2002-02-01 13:44                       ` Jim Blandy
2002-02-04  9:13                         ` Daniel Berlin
2002-02-04 17:13                           ` Andrew Cagney
2002-02-15 12:47                           ` Jim Blandy
2002-02-04 16:29                         ` Andrew Cagney
2002-01-17 15:20   ` Andrew Cagney

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=20020117180959.A2987@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=dan@dberlin.org \
    --cc=gdb@sources.redhat.com \
    --cc=petrs@caldera.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