OK.
On Mon, Dec 18, 2017 at 2:56 PM, Marek Polacek wrote:
> On Mon, Dec 18, 2017 at 01:07:18PM -0500, Jason Merrill wrote:
>> On Mon, Dec 18, 2017 at 10:09 AM, Marek Polacek wrote:
>> > Here the problem was that cxx_eval_call_expression can cache the result of
>> > a
>> > constexpr call in cons
On Mon, Dec 18, 2017 at 01:07:18PM -0500, Jason Merrill wrote:
> On Mon, Dec 18, 2017 at 10:09 AM, Marek Polacek wrote:
> > Here the problem was that cxx_eval_call_expression can cache the result of a
> > constexpr call in constexpr_call_table, but we have to be careful, after
> > store_init_value
On Mon, Dec 18, 2017 at 10:09 AM, Marek Polacek wrote:
> Here the problem was that cxx_eval_call_expression can cache the result of a
> constexpr call in constexpr_call_table, but we have to be careful, after
> store_init_value the result might be invalid. So I believe we also have to
> clear the
Here the problem was that cxx_eval_call_expression can cache the result of a
constexpr call in constexpr_call_table, but we have to be careful, after
store_init_value the result might be invalid. So I believe we also have to
clear the constexpr call table. I've lumped it together with clearing
cv
