Displaying 2 results from an estimated 2 matches for "a_strange_error".
2016 Jun 14
4
Early CSE clobbering llvm.assume
...only declared when NDEBUG is not defined.
2. Even saying that we'd get around this by ignoring parsing errors within the assert when NDEBUG is defined, but otherwise assuming the result is not desirable. There are large bodies of code which do this;
assert(i > 5);
if (i <= 5) throw a_strange_error();
so that, in production builds, the program does not crash, but instead unwinds. There are all sorts of reasons we can use to argue this is a bad coding practice, and I personally agree, but that does not change the fact that braking this idiom is not something we should do.
The contracts featu...
2016 Jun 14
3
Early CSE clobbering llvm.assume
On Tue, Jun 14, 2016 at 10:36 AM, Lawrence, Peter <c_plawre at qca.qualcomm.com
> wrote:
> Daniel,
>
> What am I missing in the following chain of logic:
>
>
>
> As far as constant-prop, value-prop, range-prop, and general
> property-propagation,
>
>
>
> 1. the compiler/optimizer **has** to get it right for if-then-else and
> while-do or