This is the mail archive of the gcc-help@gcc.gnu.org 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: How to debug LTO-related failures?

From: Martin Sebor <msebor at gmail dot com>
To: Manuel Lauss <manuel dot lauss at gmail dot com>, gcc-help <gcc-help at gcc dot gnu dot org>
Date: Tue, 20 Mar 2018 08:56:29 -0600
Subject: Re: How to debug LTO-related failures?
References: <CAOLZvyHHzSx1mrdbu7mVGR5a69ZMiwLBtXQsEGim6C+8hYNqdQ@mail.gmail.com>

On 03/16/2018 08:32 AM, Manuel Lauss wrote:

Hello,

Is there a guideline on how to best investigate LTO-related runtime
failures?  I've found
that gcc-8 r258566 miscompiles ffmpeg-3.4.2 when built with lto, and
I'd like to prepare a proper bug report.


The GCC Wiki has some suggestions:

  https://gcc.gnu.org/wiki/DebuggingGCC
  https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction

I described the approach to debugging general optimizer problems
that involve large numbers of functions or multiple files and that
has worked for me in this response:

  https://gcc.gnu.org/ml/gcc/2018-02/msg00040.html

Martin

References:
- How to debug LTO-related failures?
  - From: Manuel Lauss

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