From: Paolo Bonzini <bonzini@gnu.org>
To: GCC Patches <gcc-patches@gcc.gnu.org>, Tom Tromey <tromey@redhat.com>
Subject: Re: [incremental] Patch: FYI: initial threading in gcc
Date: Fri, 12 Oct 2007 08:57:00 -0000 [thread overview]
Message-ID: <470F36E6.4090703@gnu.org> (raw)
In-Reply-To: <m3bqb5e7ls.fsf@fleche.redhat.com>
> There are some limitations in the current patch. First, it assumes
> pthreads and the existence of __thread. Fixing this is just some
> boring configury, or perhaps figuring out how to re-use gthr* on the
> host. (If __thread is not available, I plan to have the server fall
> back to single-threaded mode.) Second, I haven't implemented PCH
> support for thread-locals.
Is there a way to do so, other than:
1) moving all globals to the heap or to GGC memory, so that they are at
least in a shared address space
2) having each thread store a pointer to its heap-allocated data both in
a thread-local variable, and in a global variable indexed by thread id.
3) having PCH look at the latter, and GCC using the former.
I fear that the above might also mean implementing pointer-swizzling on
PCH load, because you might need the same PCH in different threads.
Great job!
Paolo
next prev parent reply other threads:[~2007-10-12 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 20:34 Tom Tromey
2007-10-12 8:57 ` Paolo Bonzini [this message]
2007-10-12 16:05 ` Tom Tromey
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=470F36E6.4090703@gnu.org \
--to=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=tromey@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).