On 11/5/20 8:31 PM, Patrick Palka wrote:
On Thu, 5 Nov 2020, Patrick Palka wrote:
On Thu, 5 Nov 2020, Jason Merrill wrote:
On 11/3/20 3:43 PM, Patrick Palka wrote:
Profiling revealed that sat_hasher::equal accounts for nearly 40% of
compile time in some cmcstl2 tests.
This patch eliminates
On Thu, 5 Nov 2020, Patrick Palka wrote:
> On Thu, 5 Nov 2020, Jason Merrill wrote:
>
> > On 11/3/20 3:43 PM, Patrick Palka wrote:
> > > Profiling revealed that sat_hasher::equal accounts for nearly 40% of
> > > compile time in some cmcstl2 tests.
> > >
> > > This patch eliminates this bottlenec
On Thu, 5 Nov 2020, Jason Merrill wrote:
> On 11/3/20 3:43 PM, Patrick Palka wrote:
> > Profiling revealed that sat_hasher::equal accounts for nearly 40% of
> > compile time in some cmcstl2 tests.
> >
> > This patch eliminates this bottleneck by caching the ATOMIC_CONSTRs
> > returned by normaliz
On 11/3/20 3:43 PM, Patrick Palka wrote:
Profiling revealed that sat_hasher::equal accounts for nearly 40% of
compile time in some cmcstl2 tests.
This patch eliminates this bottleneck by caching the ATOMIC_CONSTRs
returned by normalize_atom. This in turn allows us to replace the
expensive atomi
Profiling revealed that sat_hasher::equal accounts for nearly 40% of
compile time in some cmcstl2 tests.
This patch eliminates this bottleneck by caching the ATOMIC_CONSTRs
returned by normalize_atom. This in turn allows us to replace the
expensive atomic_constraints_identical_p check in sat_hash
