summaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
diff options
context:
space:
mode:
authorFangrui Song <maskray@google.com>2020-02-04 14:28:20 -0800
committerFangrui Song <maskray@google.com>2020-02-21 15:44:14 -0800
commit75af9da755721123e62b45cd0bc0c5e688a9722a (patch)
tree336fe98d7924eeae954102d741295c959586a000 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
parent266877a2a8b2d1939f3b08fcfb711890fefc96e3 (diff)
[MC][ELF] Error for sh_type, sh_flags or sh_entsize change
Heads-up message: https://lists.llvm.org/pipermail/llvm-dev/2020-February/139390.html GNU as started to emit warnings for changed sh_type or sh_flags in 2000. GNU as>=2.35 will emit errors for most sh_type/sh_flags change, and error for entsize change. Some cases remain warnings for legacy reasons: .section .init_array,"ax", @progbits .section .init_array,"ax", @init_array # And some obscure sh_flags changes (OS/Processor specific flags) The rationale of a diagnostic (warning or error) is that sh_type, sh_flags or sh_entsize changes usually indicate user errors. The values are taken from the first .section directive. Successive directives are ignored. We just try to be rigid and emit errors for all sh_type/sh_flags/sh_entsize change. A possible improvement in the future is to reuse llvm-readobj/ELFDumper.cpp:getSectionTypeString so that we can name the type in the diagnostics. Reviewed By: psmith Differential Revision: https://reviews.llvm.org/D73999
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions