diff options
| author | YiFei Zhu <zhuyifei1999@gmail.com> | 2021-04-22 05:05:56 -0500 |
|---|---|---|
| committer | David Faust <david.faust@oracle.com> | 2021-04-23 09:56:20 -0700 |
| commit | 0a662e103e911af935aa5c601051c135986ce3de (patch) | |
| tree | 84689b4e37aef8c73067d3d055b53a0ede528464 /gcc/config/bpf | |
| parent | 716bb02b40ecef5564abb5ba45a594323123a104 (diff) | |
| download | gcc-0a662e103e911af935aa5c601051c135986ce3de.zip gcc-0a662e103e911af935aa5c601051c135986ce3de.tar.gz gcc-0a662e103e911af935aa5c601051c135986ce3de.tar.bz2 | |
bpf: align function entry point to 64 bits
Libbpf does not treat paddings after functions well. If function
symbols does not cover a whole text section, it will emit error
similar to:
libbpf: sec '.text': failed to find program symbol at offset 56
Each instruction in BPF is a multiple of 8 bytes, so align the
functions to 8 bytes, similar to how clang does it.
2021-04-22 YiFei Zhu <zhuyifei1999@gmail.com>
gcc/
* config/bpf/bpf.h (FUNCTION_BOUNDARY): Set to 64.
Diffstat (limited to 'gcc/config/bpf')
| -rw-r--r-- | gcc/config/bpf/bpf.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gcc/config/bpf/bpf.h b/gcc/config/bpf/bpf.h index 9e2f526..6a3907f 100644 --- a/gcc/config/bpf/bpf.h +++ b/gcc/config/bpf/bpf.h @@ -57,8 +57,8 @@ 64-bit at any time. */ #define STACK_BOUNDARY 64 -/* Function entry points are aligned to 128 bits. */ -#define FUNCTION_BOUNDARY 128 +/* Function entry points are aligned to 64 bits. */ +#define FUNCTION_BOUNDARY 64 /* Maximum alignment required by data of any type. */ #define BIGGEST_ALIGNMENT 64 |