Currently, -fstrip controls both debug information (typically DWARF) and symbols. However, it is common to want to strip debug information while retaining symbols, because debug information can be incredibly large. Users should not have to reach for objcopy for this use case.
#22591 attempts to solve this, though it doesn't do so when using the self-hosted backends: that task is more complex. I have not yet reviewed that PR, so do not know whether or not its implementation (for the LLVM backend) is appropriate.
Currently,
-fstripcontrols both debug information (typically DWARF) and symbols. However, it is common to want to strip debug information while retaining symbols, because debug information can be incredibly large. Users should not have to reach forobjcopyfor this use case.#22591 attempts to solve this, though it doesn't do so when using the self-hosted backends: that task is more complex. I have not yet reviewed that PR, so do not know whether or not its implementation (for the LLVM backend) is appropriate.