This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH, Darwin] Do not run dsymutil automatically, when -save-temps is on the command line.
- From: Mike Stump <mikestump at comcast dot net>
- To: Iain Sandoe <iain at sandoe dot co dot uk>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Mike Stump <mrs at gcc dot gnu dot org>, Dominique d'Humières <dominiq at lps dot ens dot fr>, FX <fxcoudert at gmail dot com>, Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Date: Mon, 20 Aug 2018 11:19:07 -0700
- Subject: Re: [PATCH, Darwin] Do not run dsymutil automatically, when -save-temps is on the command line.
- References: <820F4886-4F7F-44EA-AF84-05359791BF5B@sandoe.co.uk>
On Aug 18, 2018, at 1:17 PM, Iain Sandoe <email@example.com> wrote:
> The point of running dsymutil automatically from collect2 is that it
> (collect2, lto-wrapper, etc) might be generating or using compiler
> temporary files that will be deleted at the end of the link process.
> dsymutil requires that it can see the objects actually used in the link
> since it actually picks up the debug info from those, rather than the
> linked exe.
> When “-save-temps” is given, the objects should be preserved (if they
> are not, then that’s a bug) and therefore we don’t need to run dsymutil
> The debug experience can be better with GDB + the original objects for
> some permutations of dsymutil / GDB.
So, I think of -save-temps as a debugging thing, and as such, kinda don't want it to change anything. I don't think people use this in production to manage their builds.
I think it's an over optimization.