diff options
| author | Yonghong Song <yhs@fb.com> | 2019-04-26 15:35:51 +0000 |
|---|---|---|
| committer | Yonghong Song <yhs@fb.com> | 2019-04-26 15:35:51 +0000 |
| commit | 51a4a0d68f3761a0a0317b3bedde06a3cb44ee3d (patch) | |
| tree | c73d1ab61e58e9be64a211a7c0b269b1201a2d53 /lldb/source/Plugins/ScriptInterpreter/Python | |
| parent | 6ee3fef9a4e197aab075f6854628403c9b716dac (diff) | |
| download | llvm-51a4a0d68f3761a0a0317b3bedde06a3cb44ee3d.zip llvm-51a4a0d68f3761a0a0317b3bedde06a3cb44ee3d.tar.gz llvm-51a4a0d68f3761a0a0317b3bedde06a3cb44ee3d.tar.bz2 | |
[BPF] do not generate predefined macro bpf
"DefineStd(Builder, "bpf", Opts)" generates the following three
macros:
bpf
__bpf
__bpf__
and the macro "bpf" is due to the fact that the target language
is C which allows GNU extensions.
The name "bpf" could be easily used as variable name or type
field name. For example, in current linux kernel, there are
four places where bpf is used as a field name. If the corresponding
types are included in bpf program, the compilation error will
occur.
This patch removed predefined macro "bpf" as well as "__bpf" which
is rarely used if used at all.
Signed-off-by: Yonghong Song <yhs@fb.com>
Differential Revision: https://reviews.llvm.org/D61173
llvm-svn: 359310
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions