From: Fangrui Song <maskray@google.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Ramana Radhakrishnan <ramana.gcc@googlemail.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Plumbers session on GNU+LLVM collab?
Date: Fri, 10 Jul 2020 15:55:15 -0700 [thread overview]
Message-ID: <20200710225515.o2d7aic2qgn5ac6i@google.com> (raw)
In-Reply-To: <CAKwvOdnT5ZMjvz2_UJ4MtvDEs9+90bsDp-Rd2SnXZZ+AqebYHw@mail.gmail.com>
On 2020-07-09, 'Nick Desaulniers' via Clang Built Linux wrote:
>Hi Segher, Rasmus, and Ramana,
>I am working on finalizing a proposal for an LLVM microconference at
>plumbers, which is focusing on a lot of issues we currently face on
>the LLVM side.
>
>I'd really like to host a session with more GNU toolchain developers
>to discuss collaboration more.
>
>I was curious; are either of you planning on attending plumbers this year?
>
>If so, would such a session be interesting enough for you to attend?
Looks like a good idea. I am interested.
Perhaps Tom Stellard, Jeremy Bennett, Nathan Sidwell and Iain Sandoe have some ideas.
They have a talk about GCC/LLVM collaboration
https://gcc.gnu.org/wiki/cauldron2019#cauldron2019talks.GCC_LLVM_Collaboration_BoF
>I was curious too, who else we should explicitly invite? I ran a
>quick set analysis on who's contributed to both kernel and
><toolchain>, and the list was much much bigger than I was expecting.
>https://gist.github.com/nickdesaulniers/5330eea6f46dea93e7766bb03311d474
>89 contributors to both linux and llvm
>283 linux+gcc
>159 linux+binutils
>(No one to all four yet...also, not super scientific, since I'm using
>name+email for the set, and emails change. Point being I don't want to
>explicitly invite hundreds of people)
Might be worth sending an email to gcc@gcc.gnu.org as well.
This month's archive: https://sourceware.org/pipermail/gcc/2020-July/
prev parent reply other threads:[~2020-07-10 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 19:43 Plumbers session on GNU+LLVM collab? Nick Desaulniers
2020-07-10 22:55 ` Fangrui Song [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=20200710225515.o2d7aic2qgn5ac6i@google.com \
--to=maskray@google.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ndesaulniers@google.com \
--cc=ramana.gcc@googlemail.com \
--cc=rostedt@goodmis.org \
--cc=segher@kernel.crashing.org \
/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 NNTP newsgroup(s).