From: Nicholas Krause <xerofoify@gmail.com>
To: rguenther@suse.de
Cc: gcc@gcc.gnu.org
Subject: Multi-Threading GCC Compiler Internal Data
Date: Mon, 16 Sep 2019 18:25:00 -0000 [thread overview]
Message-ID: <211b7dc7-2535-33c5-7f6e-ed14b16cc3f2@gmail.com> (raw)
Greetings Richard,
I don't know if it's currently possible but whats the best way to either
so about or
use a tool to expose shared state at both the GIMPLE and RTL level.Â
This would
allow us to figure out much better what algorthims or data structures to
choose
to allow this to scale much better than the current prototype.
Thanks,
Nick
next reply other threads:[~2019-09-16 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 18:25 Nicholas Krause [this message]
2019-09-17 6:37 ` Richard Biener
2019-09-17 15:20 ` Nicholas Krause
2019-09-18 8:01 ` Richard Biener
2019-09-18 20:09 ` Nicholas Krause
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=211b7dc7-2535-33c5-7f6e-ed14b16cc3f2@gmail.com \
--to=xerofoify@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).