On 01/29/2014 09:18 PM, Jonathan Wakely wrote:
On 29 January 2014 20:06, François Dumont wrote:
Here is the patch that simply consider 55083 as not supported except in
normal mode. This is a temporary workaround for 4.9 release so I prefer not
to introduce a dg-profile-mode-unsupported or
On 29 January 2014 20:06, François Dumont wrote:
> Here is the patch that simply consider 55083 as not supported except in
> normal mode. This is a temporary workaround for 4.9 release so I prefer not
> to introduce a dg-profile-mode-unsupported or something like that. Those
> tests will simpl
Here is the patch that simply consider 55083 as not supported
except in normal mode. This is a temporary workaround for 4.9 release so
I prefer not to introduce a dg-profile-mode-unsupported or something
like that. Those tests will simply appear as not supported for debug and
parallel mode
Indeed, default constructor and copy constructor shall not be noexcept
qualified.
IMO we should be able to make move constructor noexcept by using a
special allocator for the underlying unordered_map that would allow to
replace an entry with an other one without requiring a
deallocate/allocat
On 26 January 2014 09:43, François Dumont wrote:
> Hi
>
> This is a patch to fix PR 55033 in profile mode. Like in debug mode it
> was missing noexcept qualifier on move constructor.
But don't those functions allocate memory? So they can throw.
I agree we want the move constructor to be noexc