If we open symlink with llvm-strip then the current behaviour is to destroy it and create
new regular file. This behaviour is different from the behaviour of binutils strip.
The new behaviour is to modify the real file and to keep symlink.
PR#59848
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I think we have made a decision (for crbug.com/1108880 c2a84771bb63947695ea50b89160c02b36fb634d @manojgupta) that we always create a new file instead of reusing the existing file.
It can be argued that our behavior has stronger security characteristics since it doesn't follow a symlink (see https://sourceware.org/bugzilla/show_bug.cgi?id=26945 ).
Perhaps we should just accept this incompatibility with GNU objcopy.