public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jose E. Marchesi <jemarch@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2254] bpf: define __bpf__ as well as __BPF__ as a target macro Date: Mon, 29 Aug 2022 20:14:48 +0000 (GMT) [thread overview] Message-ID: <20220829201448.59A213857014@sourceware.org> (raw) https://gcc.gnu.org/g:c68b5c078bbf167e6ab84fc230a53580dcc651db commit r13-2254-gc68b5c078bbf167e6ab84fc230a53580dcc651db Author: Jose E. Marchesi <jose.marchesi@oracle.com> Date: Mon Aug 29 22:13:11 2022 +0200 bpf: define __bpf__ as well as __BPF__ as a target macro LLVM defines both __bpf__ and __BPF_ as target macros. GCC was defining only __BPF__. This patch defines __bpf__ as a target macro for BPF. Tested in bpf-unknown-none. gcc/ChangeLog: * config/bpf/bpf.cc (bpf_target_macros): Define __bpf__ as a target macro. Diff: --- gcc/config/bpf/bpf.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/config/bpf/bpf.cc b/gcc/config/bpf/bpf.cc index 7e37e080808..9cb56cfb287 100644 --- a/gcc/config/bpf/bpf.cc +++ b/gcc/config/bpf/bpf.cc @@ -291,6 +291,7 @@ void bpf_target_macros (cpp_reader *pfile) { builtin_define ("__BPF__"); + builtin_define ("__bpf__"); if (TARGET_BIG_ENDIAN) builtin_define ("__BPF_BIG_ENDIAN__");
reply other threads:[~2022-08-29 20:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220829201448.59A213857014@sourceware.org \ --to=jemarch@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).