Re: [boost] [review] Outcome: internal compiler error

Subject: Re: [boost] [review] Outcome: internal compiler error
From: Niall Douglas (s_sourceforge_at_[hidden])
Date: 2018-01-27 03:40:39

> (I suspect that this is a backend ICE, if Clang/C2 reproed it too,
> but a preprocessed file will let us figure out the root cause.)

Precisely why (i.e. backend) a source file with an empty main function
instantiating nothing should never, *ever*, ICE a compiler. I mean, I'd
get why a frontend might ICE. But if you don't instantiate anything
apart from an empty main function, then the backend ought to not be
doing anything. Ever.

I'll get to submitting a repro sometime between tomorrow and Wednesday,
depending on workload. Outcome review takes precedence.

Thanks for the quick reply Stephan, and apologies for the ribbing. I
recently ran clang-tidy on AFIO which is only a three year old codebase,
and I was fairly shocked at how awful - as in, clearly hard "segfault me
now" UB - the code I had written. It happens to us all. (And well done
on whomever added to clang-tidy the "you are copy slicing an object with
multiple inheritance" lint check)

Niall

-- 
ned Productions Limited Consulting
http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/