Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c++ > #123546
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Newsgroups | comp.lang.c++ |
| Subject | Re: How to smartly deal with SIGSEGV (hazard pointers) |
| Date | 2026-03-11 12:28 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <10osfor$1cing$1@dont-email.me> (permalink) |
| References | <10omir9$3c0et$1@raubtier-asyl.eternal-september.org> <10oni0n$3p84r$1@dont-email.me> <10oomb9$3h12$1@raubtier-asyl.eternal-september.org> <10oqba1$mbce$1@dont-email.me> <10oqsse$qsnd$1@raubtier-asyl.eternal-september.org> |
On 3/10/2026 10:00 PM, Bonita Montero wrote:
> Am 11.03.2026 um 00:59 schrieb Chris M. Thomasson:
>
>> Notice where you align?
>>
>>> alignas(2 * sizeof(size_t)) head m_head = { 0, 0 };
>
> Because atomic_ref makes a runtime-check about that.
>
>> Well, I don't think a SLIST anchor is automatically aligned. ...
>
> On ARM it should.
Hopefully. ;^)
>> ? Notice _aligned_malloc?
>
> Not necessary here; the head is just a class.
Just to be tidy, so to speak. Pad _and_ align the head on a l2 cache
line, even with SLIST_HEADER. Completely isolate it. Also, for your
nodes, ditto.
>> Also, have you checked that your compare_exchange_strong is using
>> CMPXCHG8B on 32 bit systems and CMPXCHG16B on 64 bit systems? That
>> used to piss me off when it said not always lock-free.
>
> Both are lock-free for sure.
Good! What does the lock-free check from C++ give you? Ala
is_always_lock_free? Some compilers scare me iirc with sometimes
lock-free... Shit happens.
Also, for fun... Keep a counter in a "debug" or "profile" mode of your
code. It simply counts how many times the SEH fired. You are making me
reminisce about the old days... ;^)
Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-09 14:44 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-09 15:36 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-10 09:56 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-10 10:43 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-03-10 13:38 +0000
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-10 16:50 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-03-10 22:45 +0000
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-11 05:51 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-03-16 07:41 +0000
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-10 16:59 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-11 06:00 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-11 12:28 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-12 06:41 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-11 23:30 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-12 08:36 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-12 08:46 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-12 16:05 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-13 01:20 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-12 21:27 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-13 06:13 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-13 01:33 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-13 10:38 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-13 11:49 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-13 11:50 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-13 11:53 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-15 10:51 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-15 13:58 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Bonita Montero <Bonita.Montero@gmail.com> - 2026-03-16 09:06 +0100
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-16 12:03 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) Tristan Wibberley <tristan.wibberley+netnews2@alumni.manchester.ac.uk> - 2026-03-17 00:04 +0000
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-16 18:13 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-10 18:24 -0700
Re: How to smartly deal with SIGSEGV (hazard pointers) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-03-10 17:27 -0700
csiph-web