On Fri, 15 Nov 2019, Alexandre Oliva wrote:
> On Nov 14, 2019, Alexandre Oliva <ol...@adacore.com> wrote:
>
> > %{!c:%{!S:-dumpbase %b}
>
> Uhh, I failed to adjust this one to add the executable output name to
> dumpbase.
>
> Anyway, getting the right semantics out of specs is providing to be a
> lot trickier than I had anticipated. I'm now pondering a single spec
> function to deal with all of these dumpbase possibilities.
>
> I'm also a little uncertain about behavior change WRT .dwo files.
> Though their names are built out of the .o files in the objcopy
> commands, they're built from aux_base_name in dwarf2out. Currently,
> since aux_base_name is derived from the output object file name, this
> ensures they have the same name and directory, but once we enable
> -dumpdir to be specified to override it, that may no longer be the
> case. Ugh...
Hmm, -dwo-base-name to the rescue? ;) Well, I guess the debug info
has to somewhere encode the full/relative path to the .dwo files
so all that is needed is to keep that consistent?
Richard.
