> On 24 May 2026, at 14:02, Sergey Bugaev <[email protected]> wrote: > > ...why cannot it? What would prevent it from doing so? These are still > just memory loads, and the problematic instruction is a perfectly fine > way to do memory loads as far as the compiler is concerned, right? > (Was this suggested by an LLM?) > > What you really want to prevent issues like that is either building > this function (or perhaps this whole file) with a compiler option that > explicitly tells it to avoid those sorts of assumptions / > instructions, or as a simpler hack, using volatile. Yes, this was indeed suggested by the LLM, my C is a bit rusty, have been working with higher level languages and projects for too long, should have spotted this. volatile indeed works and is the proper way to fix this. Will fix it for v2
Re: [RFC PATCH 09/18] device/dtb: read 8-byte cells as two 4-byte loads to survive pre-MMU access
Paulo Fernando Barbosa Duarte Sun, 24 May 2026 13:41:02 -0700
- Re: [RFC PATCH 17/18] tests: aarch64 ar... Sergey Bugaev
- Re: [RFC PATCH 17/18] tests: aarch6... Paulo Fernando Barbosa Duarte
- [RFC PATCH 06/18] ipc: declare copyinmsg / c... Paulo Duarte
- [RFC PATCH 03/18] aarch64: drop the ramdisk ... Paulo Duarte
- Re: [RFC PATCH 03/18] aarch64: drop the... Sergey Bugaev
- Re: [RFC PATCH 03/18] aarch64: drop... Paulo Fernando Barbosa Duarte
- Re: [RFC PATCH 03/18] aarch64: ... Sergey Bugaev
- Re: [RFC PATCH 03/18] aarch... Paulo Fernando Barbosa Duarte
- [RFC PATCH 09/18] device/dtb: read 8-byte ce... Paulo Duarte
- Re: [RFC PATCH 09/18] device/dtb: read ... Sergey Bugaev
- Re: [RFC PATCH 09/18] device/dtb: r... Paulo Fernando Barbosa Duarte
- [RFC PATCH 08/18] aarch64: move boot stack o... Paulo Duarte
- Re: [RFC PATCH 08/18] aarch64: move boo... Sergey Bugaev
- Re: [RFC PATCH 08/18] aarch64: move... Paulo Fernando Barbosa Duarte
- Re: [RFC PATCH 08/18] aarch64: ... Sergey Bugaev
- Re: [RFC PATCH 08/18] aarch... Paulo Fernando Barbosa Duarte
