From: Yonghong Song <yhs@fb.com> To: "Jose E. Marchesi" <jose.marchesi@oracle.com>, "bpf@vger.kernel.org" <bpf@vger.kernel.org> Subject: initiated discussion to support attribute address_space in clang Date: Thu, 24 Oct 2019 16:56:06 +0000 [thread overview] Message-ID: <79a43f7f-b463-5f40-7830-f488d178b0a4@fb.com> (raw) In-Reply-To: <87lfutgvsu.fsf@oracle.com> Hi, Jose, I just initiated a discussion (RFC patch https://reviews.llvm.org/D69393) for llvm/clang to support user address_space attribute. I am not able to add your name in subscriber list as you probably not registered with llvm mailing list or phabricator. Just let you know so we can have an eventual proposal which will be also good for gcc. Please participate in discussion. Thanks, Yonghong
next prev parent reply other threads:[~2019-10-24 16:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-09-12 19:26 [GCC,LLVM] bpf_helpers.h Jose E. Marchesi 2019-09-16 16:18 ` Alexei Starovoitov 2019-09-17 13:17 ` Jose E. Marchesi 2019-10-24 16:56 ` Yonghong Song [this message] 2019-11-04 10:21 ` initiated discussion to support attribute address_space in clang Jose E. Marchesi 2019-11-07 6:49 ` Yonghong Song
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=79a43f7f-b463-5f40-7830-f488d178b0a4@fb.com \ --to=yhs@fb.com \ --cc=bpf@vger.kernel.org \ --cc=jose.marchesi@oracle.com \ --subject='Re: initiated discussion to support attribute address_space in clang' \ /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
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).