This is the mail archive of the
mailing list for the GCC project.
Re: Status of GCC 6 on x86_64 (Debian)
- From: Markus Trippelsdorf <markus at trippelsdorf dot de>
- To: Martin Michlmayr <tbm at hpe dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 22 Jan 2016 20:42:07 +0100
- Subject: Re: Status of GCC 6 on x86_64 (Debian)
- Authentication-results: sourceware.org; auth=none
- References: <20160122050903 dot GA2912 at jirafa dot cyrius dot com> <20160122192713 dot GA12977 at jirafa dot cyrius dot com>
On 2016.01.22 at 11:27 -0800, Martin Michlmayr wrote:
> * Martin Michlmayr <firstname.lastname@example.org> [2016-01-21 21:09]:
> > * 13: test suite failures (segfaults and similar); not clear if the
> > package or if GCC is at fault.
> Rene Engelhard pointed me to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69327
> which might explain some of these segfaults.
My guess would be that most segfaults are caused by the much more
aggressive optimization based on the assumption that "this" must never
be NULL in C++.
QT5, Chromium and Kdevelop all call methods from a NULL pointer and
crash for this reason. -fno-delete-null-pointer-checks is a workaround.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68853 for an analysis
of the Chromium crash.