public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Fedora 14 branches merge by 2010-07-27
Date: Thu, 08 Jul 2010 01:51:00 -0000	[thread overview]
Message-ID: <m3zky27nbr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100707205847.GA9664@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Wed, 7 Jul 2010 22:58:47 +0200")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> These branches probably remain:
Jan>   archer-tromey-delayed-symfile2

I think this will be obsoleted by the index work.

Jan> Please comment these branches:
Jan>   archer-tromey-optional-psymtab
Jan>     = Make psymtabs optional; implement DWARF indexing proposal

Yes, we should ship this.
I'm still hoping we can get all the patches in upstream soon.
The branch is not really in an ideal state, but I will send a patch
series once it is all ready (or rebase on the version you specified &
push my patch-preparation branch).

Jan>   archer-tromey-threaded-dwarf
Jan>     = A branch off optional-psymtab that reads indices in background threads.

Don't know yet.  It would need a bit of work.

Jan>   archer-tromey-imported-unit
Jan>     = Support for DW_TAG_imported_unit. Untested.

Nope.  We don't need this until the dwarf compressor is done, and even
once it is done we have to test this branch & fix bugs.

Tom

  reply	other threads:[~2010-07-08  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 20:58 Jan Kratochvil
2010-07-08  1:51 ` Tom Tromey [this message]
2010-07-08  9:52 ` Phil Muldoon
2010-07-08 15:37 ` Keith Seitz
2010-07-08 15:43   ` Jan Kratochvil
2010-07-08 18:35 ` Tom Tromey
2010-07-09 16:48 ` Fedora 14 branches merge by 2010-07-27 [new list] Jan Kratochvil

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=m3zky27nbr.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).