diff options
author | Fangrui Song <i@maskray.me> | 2024-08-19 18:20:02 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-08-19 18:20:02 -0700 |
commit | d3864d946a178807bb5a87d3d1690e213c89e5be (patch) | |
tree | 6a4d7eb6377c75b4ef51f5519e0883432338ad1a /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp | |
parent | b5f3e28eca9bae94412415e5a77f769cf1e4fc61 (diff) | |
download | llvm-d3864d946a178807bb5a87d3d1690e213c89e5be.zip llvm-d3864d946a178807bb5a87d3d1690e213c89e5be.tar.gz llvm-d3864d946a178807bb5a87d3d1690e213c89e5be.tar.bz2 |
[Driver] Default -msmall-data-limit= to 0 and clean up code
D57497 added -msmall-data-limit= as an alias for -G and defaulted it to 8 for
-fno-pic/-fpie.
The behavior is already different from GCC in a few ways:
* GCC doesn't accept -G.
* GCC -fpie doesn't seem to use -msmall-data-limit=.
* GCC emits .srodata.cst* that we don't use (#82214). Writable contents
caused confusion (https://bugs.chromium.org/p/llvm/issues/detail?id=61)
In addition,
* claiming `-shared` means we don't get a desired `-Wunused-command-line-argument` for `clang --target=riscv64-linux-gnu -fpic -c -shared a.c`.
* -mcmodel=large doesn't work for RISC-V yet, so the special case is strange.
* It's quite unusual to emit a warning when an option (unrelated to relocation model) is used with -fpic.
* We don't want future configurations (Android) to continue adding customization to `SetRISCVSmallDataLimit`.
I believe the extra code just doesn't pull its weight and should be
cleaned up. This patch also changes the default to 0. GP relaxation
users are encouraged to specify these customization options explicitly.
Pull Request: https://github.com/llvm/llvm-project/pull/83093
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions