From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: LIU Hao <lh_mouse@126.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: why does gccgit require pthread?
Date: Mon, 7 Nov 2022 13:51:38 +0000 [thread overview]
Message-ID: <CAH6eHdSbUTk636yj=zgp-z1ra2Z38T-KWPNKPaW=gWBfYegnwA@mail.gmail.com> (raw)
In-Reply-To: <0c6b1411-fa35-1c2f-16f2-f26b6e6cedaa@126.com>
On Mon, 7 Nov 2022 at 13:33, LIU Hao wrote:
>
> 在 2022-11-07 20:57, Jonathan Wakely 写道:
> > It would be a lot nicer if playback::context met the C++ Lockable
> > requirements, and playback::context::compile () could just take a
> > scoped lock on *this:
> >
> >
>
> Yeah yeah that makes a lot of sense. Would you please just commit that? I don't have write access to
> GCC repo, and it takes a couple of hours for me to bootstrap GCC just for this tiny change.
Somebody else needs to approve it first. I'll combine our patches and
test and submit it properly for approval.
next prev parent reply other threads:[~2022-11-07 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8f15b063-9ec8-59e0-590b-20e416f68cb4@126.com>
[not found] ` <CA+=Sn1ncp6hN8MnziZ+2f-6_UUqMwXeVGQLmft2NUeuXGOaBoA@mail.gmail.com>
2022-11-07 6:50 ` LIU Hao
2022-11-07 7:03 ` Andrew Pinski
2022-11-07 7:10 ` LIU Hao
2022-11-07 12:57 ` Jonathan Wakely
2022-11-07 13:33 ` LIU Hao
2022-11-07 13:51 ` Jonathan Wakely [this message]
2022-11-11 17:16 ` Jonathan Wakely
2022-11-11 18:27 ` Jonathan Wakely
2022-11-14 10:54 ` LIU Hao
2022-11-15 18:50 ` why does gcc jit " David Malcolm
2022-11-15 19:01 ` Jonathan Wakely
2022-11-19 11:27 ` Jonathan Wakely
2022-11-19 12:51 ` LIU Hao
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='CAH6eHdSbUTk636yj=zgp-z1ra2Z38T-KWPNKPaW=gWBfYegnwA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=lh_mouse@126.com \
--cc=pinskia@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).