public inbox for archer-commits@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: archer-commits@sourceware.org
Subject: [SCM]  archer-tromey-threaded-dwarf: add README.archer
Date: Fri, 22 Feb 2013 17:19:00 -0000	[thread overview]
Message-ID: <20130222171940.16839.qmail@sourceware.org> (raw)

The branch, archer-tromey-threaded-dwarf has been updated
       via  f46dc58dcb881b653021700a45c8f92c7b616892 (commit)
      from  e0418e92bde228efd50f5305014969ff17b58ed0 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit f46dc58dcb881b653021700a45c8f92c7b616892
Author: Tom Tromey <tromey@redhat.com>
Date:   Fri Feb 22 09:31:29 2013 -0700

    add README.archer

-----------------------------------------------------------------------

Summary of changes:
 README.archer |   12 ++++++++++++
 1 files changed, 12 insertions(+), 0 deletions(-)
 create mode 100644 README.archer

First 500 lines of diff:
diff --git a/README.archer b/README.archer
new file mode 100644
index 0000000..8222685
--- /dev/null
+++ b/README.archer
@@ -0,0 +1,12 @@
+This branch has some experimental code for making psymtabs for DWARF
+in worker threads.  It has some generic changes to gdb and BFD for
+thread-awareness, and changes to the DWARF reader to make it work in
+the background.
+
+It still has a few issues.  The "complaint" system is not thread-safe
+and the BFD file descriptor cache is still somewhat broken.  There may
+be lurking problems.
+
+The biggest issue is that this didn't really help much for
+performance.  It might in some situations, but it isn't an unqualified
+win.


hooks/post-receive
--
Repository for Project Archer.


                 reply	other threads:[~2013-02-22 17:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20130222171940.16839.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=archer-commits@sourceware.org \
    /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).