On 12/14/2015 07:49 PM, Trevor Saunders wrote:
+ hash_map (const hash_map &h, bool ggc = false,
+ bool gather_mem_stats = true CXX_MEM_STAT_INFO)
sorry about the late response, but wouldn't it be better to make this
and the hash_table constructor explicit? Its probably less importa
>
> + hash_map (const hash_map &h, bool ggc = false,
> + bool gather_mem_stats = true CXX_MEM_STAT_INFO)
sorry about the late response, but wouldn't it be better to make this
and the hash_table constructor explicit? Its probably less important
than other constructors, but is there a re
On Fri, Dec 11, 2015 at 8:05 PM, Jason Merrill wrote:
> On 12/11/2015 05:10 AM, Richard Biener wrote:
>>
>> On Thu, Dec 10, 2015 at 11:03 PM, Jason Merrill wrote:
>>>
>>> The C++ front end uses a temporary hash table to remember specializations
>>> of
>>> local variables during template instantia
On 12/11/2015 05:10 AM, Richard Biener wrote:
On Thu, Dec 10, 2015 at 11:03 PM, Jason Merrill wrote:
The C++ front end uses a temporary hash table to remember specializations of
local variables during template instantiations. In a nested function such
as a lambda or local class member function
On Thu, Dec 10, 2015 at 11:03 PM, Jason Merrill wrote:
> The C++ front end uses a temporary hash table to remember specializations of
> local variables during template instantiations. In a nested function such
> as a lambda or local class member function, we need to retain the elements
> from the
The C++ front end uses a temporary hash table to remember
specializations of local variables during template instantiations. In a
nested function such as a lambda or local class member function, we need
to retain the elements from the enclosing function's
local_specializations table; otherwise
