This is also one of many good reasons to not make allocators
library based, but do it in the compiler and backend. That also
allows you do allocate multiple objects in a single CAS. (i.e.
the compiler collects multiple allocs calls and replace it with
one)
- Re: The GC and performance... Steven Schveighoffer via Digitalmars-d
- Re: The GC and performance... Atila Neves via Digitalmars-d
- Re: The GC and performance, bu... Martin Nowak via Digitalmars-d
- Re: The GC and performance, but not... Brian Schott via Digitalmars-d
- Re: The GC and performance, bu... Marco Leise via Digitalmars-d
- Re: The GC and performance, bu... Nordlöw
- Re: The GC and performance, but not... Sean Kelly via Digitalmars-d
- Re: The GC and performance, but not... Rainer Schuetze via Digitalmars-d
- Re: The GC and performance, bu... Marco Leise via Digitalmars-d
- Re: The GC and performance... via Digitalmars-d
- Re: The GC and perform... via Digitalmars-d
- Re: The GC and perform... Marco Leise via Digitalmars-d
- Re: The GC and per... Kagamin via Digitalmars-d
- Re: The GC an... Marco Leise via Digitalmars-d
- Re: The GC and performance, bu... Adam Sakareassen via Digitalmars-d
- Re: The GC and performance, bu... Nordlöw
- Re: The GC and performance... Adam Sakareassen via Digitalmars-d
- Re: The GC and performance... Nordlöw
- Re: The GC and performance, bu... Etienne via Digitalmars-d