diff options
author | Peter Zijlstra <peterz@infradead.org> | 2024-11-08 10:32:02 +0100 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2024-11-11 11:49:42 +0100 |
commit | d5173f7537505315557d8580e3a648f07f17deda (patch) | |
tree | 039321c9a1d0407b4c9873de02795935a848eb01 /include/uapi | |
parent | 56ac7bd2c58a4e93d19f0ccb181035d075b315d3 (diff) | |
download | lwn-d5173f7537505315557d8580e3a648f07f17deda.tar.gz lwn-d5173f7537505315557d8580e3a648f07f17deda.zip |
objtool: Exclude __tracepoints data from ENDBR checks
For some, as of yet unexplained reason, Clang-19, but not GCC,
generates and endless stream of:
drivers/iio/imu/bno055/bno055_ser.o: warning: objtool: __tracepoint_send_chunk+0x20: data relocation to !ENDBR: __SCT__tp_func_send_chunk+0x0
drivers/iio/imu/bno055/bno055_ser.o: warning: objtool: __tracepoint_cmd_retry+0x20: data relocation to !ENDBR: __SCT__tp_func_cmd_retry+0x0
drivers/iio/imu/bno055/bno055_ser.o: warning: objtool: __tracepoint_write_reg+0x20: data relocation to !ENDBR: __SCT__tp_func_write_reg+0x0
drivers/iio/imu/bno055/bno055_ser.o: warning: objtool: __tracepoint_read_reg+0x20: data relocation to !ENDBR: __SCT__tp_func_read_reg+0x0
drivers/iio/imu/bno055/bno055_ser.o: warning: objtool: __tracepoint_recv+0x20: data relocation to !ENDBR: __SCT__tp_func_recv+0x0
Which is entirely correct, but harmless. Add the __tracepoints section
to the exclusion list.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Link: https://lkml.kernel.org/r/20241108184618.GG38786@noisy.programming.kicks-ass.net
Diffstat (limited to 'include/uapi')
0 files changed, 0 insertions, 0 deletions