Re: [C++ Patch] PR 81054 ("[7/8 Regression] ICE with volatile variable in constexpr function") [Take 2]

2018-01-17 Thread Jason Merrill
OK. On Wed, Jan 17, 2018 at 11:16 AM, Paolo Carlini wrote: > Hi, > > On 17/01/2018 15:58, Jason Merrill wrote: >> >> On Tue, Jan 16, 2018 at 4:40 PM, Paolo Carlini >> wrote: >>> >>> On 16/01/2018 22:35, Jason Merrill wrote: On Tue,

Re: [C++ Patch] PR 81054 ("[7/8 Regression] ICE with volatile variable in constexpr function") [Take 2]

2018-01-17 Thread Paolo Carlini
Hi, On 17/01/2018 15:58, Jason Merrill wrote: On Tue, Jan 16, 2018 at 4:40 PM, Paolo Carlini wrote: On 16/01/2018 22:35, Jason Merrill wrote: On Tue, Jan 16, 2018 at 3:32 PM, Paolo Carlini wrote: thus I figured out what was badly wrong in

Re: [C++ Patch] PR 81054 ("[7/8 Regression] ICE with volatile variable in constexpr function") [Take 2]

2018-01-17 Thread Jason Merrill
On Tue, Jan 16, 2018 at 4:40 PM, Paolo Carlini wrote: > On 16/01/2018 22:35, Jason Merrill wrote: >> On Tue, Jan 16, 2018 at 3:32 PM, Paolo Carlini >> wrote: >>> >>> thus I figured out what was badly wrong in my first try: I misread >>>

Re: [C++ Patch] PR 81054 ("[7/8 Regression] ICE with volatile variable in constexpr function") [Take 2]

2018-01-16 Thread Paolo Carlini
.. regression testing actually completed successfully. Paolo.

Re: [C++ Patch] PR 81054 ("[7/8 Regression] ICE with volatile variable in constexpr function") [Take 2]

2018-01-16 Thread Paolo Carlini
Hi Jason On 16/01/2018 22:35, Jason Merrill wrote: On Tue, Jan 16, 2018 at 3:32 PM, Paolo Carlini wrote: thus I figured out what was badly wrong in my first try: I misread ensure_literal_type_for_constexpr_object and missed that it can return NULL_TREE without

Re: [C++ Patch] PR 81054 ("[7/8 Regression] ICE with volatile variable in constexpr function") [Take 2]

2018-01-16 Thread Jason Merrill
On Tue, Jan 16, 2018 at 3:32 PM, Paolo Carlini wrote: > thus I figured out what was badly wrong in my first try: I misread > ensure_literal_type_for_constexpr_object and missed that it can return > NULL_TREE without emitting an hard error. Thus my first try even caused >