From: Oleg Endo <oleg.endo@t-online.de>
To: Richard Biener <richard.guenther@gmail.com>,
Giuliano Belinassi <giuliano.belinassi@usp.br>
Cc: GCC Development <gcc@gcc.gnu.org>,
kernel-usp@googlegroups.com, gold@ime.usp.br,
Alfredo Goldman <alfredo.goldman@gmail.com>
Subject: Re: Parallelize the compilation using Threads
Date: Sat, 16 Feb 2019 04:35:00 -0000 [thread overview]
Message-ID: <e6bdcfad18cf8107d20b872e87b433643e351379.camel@t-online.de> (raw)
In-Reply-To: <CAFiYyc3Gt9khFX+J5wBKs6h3D3e=1CT343SL9sy_GUpvqboDyQ@mail.gmail.com>
On Tue, 2019-02-12 at 15:12 +0100, Richard Biener wrote:
> On Mon, Feb 11, 2019 at 10:46 PM Giuliano Belinassi
> <giuliano.belinassi@usp.br> wrote:
> >
> > Hi,
> >
> > I was just wondering what API should I use to spawn threads and
> > control
> > its flow. Should I use OpenMP, pthreads, or something else?
> >
> > My point what if we break compatibility with something. If we use
> > OpenMP, I'm afraid that we will break compatibility with compilers
> > not
> > supporting it. On the other hand, If we use pthread, we will break
> > compatibility with non-POSIX systems (Windows).
>
> I'm not sure we have a thread abstraction for the host - we do have
> one for the target via libgcc gthr.h though. For prototyping I'd
> resort
> to this same interface and fixup the host != target case as needed.
Or maybe, in the year 2019, we could assume that most c++ compilers
which are used to compile GCC support c++11 and come with an adequate
<thread> implementation... yeah, I know, sounds jacked :)
Cheers,
Oleg
prev parent reply other threads:[~2019-02-16 4:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 10:12 Giuliano Augusto Faulin Belinassi
2018-11-15 11:44 ` Richard Biener
2018-11-15 15:54 ` Jonathan Wakely
2018-11-15 18:07 ` Jeff Law
2018-11-15 18:36 ` Szabolcs Nagy
2018-11-16 14:25 ` Martin Jambor
2018-11-16 22:40 ` Giuliano Augusto Faulin Belinassi
2018-11-19 14:36 ` Richard Biener
2018-12-12 15:46 ` Giuliano Augusto Faulin Belinassi
2018-12-13 8:12 ` Bin.Cheng
2018-12-14 14:15 ` Giuliano Belinassi
2018-12-17 11:06 ` Richard Biener
2019-01-14 11:42 ` Giuliano Belinassi
2019-01-14 12:23 ` Richard Biener
2019-01-15 21:45 ` Giuliano Belinassi
2019-01-16 12:44 ` Richard Biener
2019-02-07 14:14 ` Giuliano Belinassi
2019-02-11 21:46 ` Giuliano Belinassi
2019-02-12 14:12 ` Richard Biener
2019-02-16 4:35 ` Oleg Endo [this message]
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=e6bdcfad18cf8107d20b872e87b433643e351379.camel@t-online.de \
--to=oleg.endo@t-online.de \
--cc=alfredo.goldman@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=giuliano.belinassi@usp.br \
--cc=gold@ime.usp.br \
--cc=kernel-usp@googlegroups.com \
--cc=richard.guenther@gmail.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).