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: Help in tracking down unusual apparent 5.2.0 LTO issue


On 2016.03.17 at 11:50 -0500, Matt Godbolt wrote:
> Hi,
> 
> I confirmed we're passing -std=c++1y in both cases (yes; this has
> bitten us before so we're sensitive to this! :). That said; I believe
> the list ABI change was guarded with new namespaces (as was the
> std::string changes that came alongside).
> 
> There's no ODR violations that we can find. We build with -Wall
> -Wextra -Werror and have seen ODR errors reported during LTO before,
> but do not have any in this project.  We run (a debug version) with
> -fsanitize=undefined (or at least a subset of undefined behaviour),
> and that's clean. The subset does not include "taking reference to a
> null pointer" as this is something parts of our code do. (None
> involving std::function or any lists).

Hmm, this sounds like -fno-delete-null-pointer-checks may help.

-- 
Markus


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