Corentin Jabot
Corentin Jabot
Fixed in 18 https://gcc.godbolt.org/z/M9PoqGohY
Fixed in trunk (post 17)
Yes, please! Here is what it looks like in Konsole, it is incredibly useful 
Note that the problem doesn't appear at `O0` so it's likely an optimization bug. Any insight @zygoloid ?
Maybe generous reading: Allocations can fail http://eel.is/c++draft/basic.stc.dynamic#allocation-2.sentence-4 If it does, in this case, `new` would throw, which would make this not a constant expression. So I think there is already...
This turns out to be... complicated. This specific issue is easy enough, to fix, I'll probably make a patch. But let's assume we allocate an array of size smaller than...
More spit balling. I'm wondering whether this is fixable at all. We should fix `APValue::Arr` construction by making sure we can handle allocation failure - we need to be slightly...
> We might want to consider an "extremely large allocation allocator" that uses lower-level OS facilities for performing the allocations so that we can catch these faults and use them...
> Agreed that we should not be constant folding until we crash, but still disagreed on the host vs target distinction. There's no relationship between host and target in general,...
I did more research, I think i have a potential solution to guarantee diagnostics, although i don't have a prototype yet: When allocating an array of app value, we could:...