Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com, mec.gnu@mindspring.com
Subject: Re: Branch created for inter-compilation-unit references
Date: Wed, 25 Feb 2004 02:23:00 -0000	[thread overview]
Message-ID: <403C0730.3000706@gnu.org> (raw)
In-Reply-To: <20040225012902.GA11745@nevyn.them.org>

[I dropped the nameless r6k, they bounced my e-mail]

> On Tue, Feb 24, 2004 at 07:35:15PM -0500, Andrew Cagney wrote:
> 
>>>> >I will start submitting preliminary patches, those which can also act
>>>> >as bug-fixes or optimizations to the current dwarf2 code, tonight or
>>>> >tomorrow.  Merging the branch may have to wait until after GDB 6.1.
>>>> >Personally, I'd love for it to be included, since the sooner we release
>>>> >a GDB that can understand this data the sooner GCC can emit it by
>>>> >default; but I want at least some more testing on the branch before
>>>> >I suggest that.  My timing for this project was somewhat unfortunate.
>>
>>> 
>>> Er, given that GCC 3.4 branch is emiting DW_OP_piece, isn't that more 
>>> urgent?
> 
> 
> Probably.  As I said, I try to do large projects roughly FIFO, and this
> has been on my TODO list a lot longer than DW_OP_piece has.

> If you're interested in DW_OP_piece support for 6.1, I can certainly
> look into it after this is done.  It will probably be less work.  I
> don't want to try to juggle two large dwarf2 projects at the same time,
> though.

In terms of getting ICU "done", talk about bad timing.  I suspect 
everyone's concentration is as directed towards 6.1 and other more 
urgent issues - this right now is far from peoples minds (I've, for 
instance, been simply deleting your patches).

Andrew



  reply	other threads:[~2004-02-25  2:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-21 20:08 Daniel Jacobowitz
2004-02-25  0:18 ` Daniel Jacobowitz
2004-02-25  0:35   ` Andrew Cagney
2004-02-25  1:29     ` Daniel Jacobowitz
2004-02-25  2:23       ` Andrew Cagney [this message]
2004-02-25  2:27         ` Daniel Jacobowitz
2004-02-25  3:17           ` Andrew Cagney
2004-02-25  3:51 Michael Elizabeth Chastain
2004-02-25  5:12 ` Andrew Cagney
2004-02-25 16:10   ` Daniel Berlin
2004-02-25 17:01     ` Andrew Cagney
2004-02-25 17:07       ` Daniel Berlin
2004-02-25 18:50         ` Andrew Cagney
2004-02-25 18:53           ` Daniel Berlin
2004-02-25 19:48             ` Andrew Cagney
2004-02-26  5:48             ` Eli Zaretskii
2004-02-26  6:06               ` Daniel Berlin
2004-02-26  6:31                 ` Eli Zaretskii
2004-02-26 15:05                   ` Daniel Jacobowitz
2004-02-26 16:19                     ` Elena Zannoni
2004-02-26 16:25                       ` Daniel Jacobowitz
2004-02-26 16:36                         ` Elena Zannoni
2004-02-26 16:54                           ` Daniel Jacobowitz
2004-02-26 19:01                           ` Eli Zaretskii
2004-02-26 19:10                     ` Eli Zaretskii
2004-02-26 19:24                     ` Andrew Cagney
2004-02-26 19:28                       ` Daniel Jacobowitz
2004-02-26 20:19                         ` Andrew Cagney
2004-02-26  5:48         ` Eli Zaretskii

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=403C0730.3000706@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb@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