public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Giuliano Belinassi <giuliano.belinassi@usp.br>
To: Richard Biener <richard.guenther@gmail.com>
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: Mon, 11 Feb 2019 21:46:00 -0000	[thread overview]
Message-ID: <20190211214624.3liqkdhb64engnja@smtp.gmail.com> (raw)
In-Reply-To: <CAFiYyc0HMDtPLJKkkYhFULBbGt8n-41fWaMtqLNmUOu9gird7w@mail.gmail.com>

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).

Giuliano.

  parent reply	other threads:[~2019-02-11 21:46 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 [this message]
2019-02-12 14:12         ` Richard Biener
2019-02-16  4:35           ` Oleg Endo

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=20190211214624.3liqkdhb64engnja@smtp.gmail.com \
    --to=giuliano.belinassi@usp.br \
    --cc=alfredo.goldman@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --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).