This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Debugging offload compiler ICEs

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 ends invoked from the target compilation's
>> > collect2 process, via the respective offloading toolchain's mkoffload.
>> Does -v -save-temps not provide enough info to re-launch the lto1 process?
> Actually, given very limited testing I have just done, that indeed seems
> to work fine now, for re-running the actual offload compiler invocation
> (driver as well as lto1 directly).  Good!  (As far as I remember, it used
> not to work a few months ago, with relevant files not having been
> preserved; that's where I got the idea from for this "pause" hack.)  To
> re-run the mkoffload invoked before, you'll need to set (several?)
> environment variables.

Yeah, for example debugging things like lto-wrapper itself that is also
required.  But cut&pasting the lto1 command should work (if not we should
fix that).


> GrÃÃe
>  Thomas

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]