On Thu, Jan 08, 2015 at 07:32:13PM +0300, Ilya Verbin wrote:
> On 08 Jan 16:49, Jakub Jelinek wrote:
> > BTW, today when looking at the TARGET_OPTION_NODE streaming caused
> > regressions, I've discovered that it is very hard to debug issues in the
> > offloading compiler. Would be nice if
> > -save-temps -v
> > printed enough information that it is actually possible to reproduce it,
> > e.g. while mkoffload command is printed, one can't cut and paste it easily,
> > because some env vars are required and those aren't printed in the -v dump.
>
> I agree, this should be improved. Unfortunately, I didn't have time so far.
>
> > Similarly, the lto1 offloading compiler invocation is not printed, and
>
> It can be printed by -foffload="-save-temps -v", or should we pass through
> these
> options from host to offload compiler by default?
Certainly not if they weren't passed by the user to the host compiler.
But if they have been passed, it might be useful, having to add -save-temps -v
to too many spaces is annoying.
And it would be really nice to print the essential env vars mkoffload is
relying on, like:
var1=value1
var2=value2
...../mkoffload /tmp/@ccABCDEF
Jakub
