Re: Debugging offload compiler ICEs

2016-05-03 Thread Richard Biener
On Tue, May 3, 2016 at 1:19 PM, Thomas Schwinge wrote: > Hi! > > On Tue, 3 May 2016 12:54:23 +0200, Richard Biener > wrote: >> On Tue, May 3, 2016 at 12:47 PM, Thomas Schwinge >> wrote: >> > It is currently difficult to debug offloading compiler invocations. >> > These are actually lto1 front e

Re: Debugging offload compiler ICEs

2016-05-03 Thread Thomas Schwinge
Hi! On Tue, 3 May 2016 12:54:23 +0200, Richard Biener wrote: > On Tue, May 3, 2016 at 12:47 PM, Thomas Schwinge > wrote: > > It is currently difficult to debug offloading compiler invocations. > > These are actually lto1 front ends invoked from the target compilation's > > collect2 process, via

Re: Debugging offload compiler ICEs

2016-05-03 Thread Richard Biener
On Tue, May 3, 2016 at 12:47 PM, Thomas Schwinge wrote: > Hi! > > It is currently difficult to debug offloading compiler invocations. > These are actually lto1 front ends invoked from the target compilation's > collect2 process, via the respective offloading toolchain's mkoffload. > To the best of

Debugging offload compiler ICEs

2016-05-03 Thread Thomas Schwinge
Hi! It is currently difficult to debug offloading compiler invocations. These are actually lto1 front ends invoked from the target compilation's collect2 process, via the respective offloading toolchain's mkoffload. To the best of my knowledge, it's not possible to use the target compiler's "-wrap