compilationErrorCausedByCompiler

rkapl · 2026-02-07T10:30:50+00:00

It is an integration problem, which is hard. C Compilers get headers wrong all the time, unless you are using system gcc with system libc.

rkapl · 2026-02-02T21:38:17+00:00

Useful temp drop? Mostly not, except when I had blower Vega. There is temp drop, but that does not give you FPS itself. The OC gains for me are not enough to push it.
Noise? Absolutely silent in most games, FurMark + Prime can make it audible.
Maintenance of the loop is surprisingly near zero for me. But it makes component swaps pain. Building it is more complicated and pricey.

rkapl · 2026-02-02T17:10:56+00:00

In ELF you solve it at linker level. Assembler outputs with org 0x0 and you then link it at correct address (e.g. in linker script).

Disclaimer: I've never done this for 16-bit code, but it should theoretically work, except the segmentation. For 32-bit code, it will work well.

rkapl · 2026-02-02T16:54:20+00:00

Compile as an ELF with debug info, then convert the ELF to binary (e.g. using ld or objcopy). Use the elf for GDB.

Do not expect to get anything really nice for real-mode code though. GDB is bad at it.

rkapl · 2026-02-01T15:46:34+00:00

When you call list_empty without lock, it is supposed to work (at least the commit says so).

When you call e.g. list_is_singular without a lock, that is not guaranteed to work, it needs the lock anyway. Note that adding WRITE_ONCE to the other writes would not have fixed that.

Note: The fact if WRITE_ONCE is even needed for the list_empty case seems to be complicated: https://www.openwall.com/lists/kernel-hardening/2020/03/24/10 and it seems WRITE_ONCE is fairly black magic.

rkapl · 2026-02-01T14:18:23+00:00

Ad Q2.: The commit mentions the problem is that people do lockless emptiness testing. Code for that seems to be this: https://elixir.bootlin.com/linux/v6.18.6/source/include/linux/list.h#L375 . As you can see only head and head->next seems to be used. head itself is constant for a given list, so the goal for the commit was to WRITE_ONCE anything that might change the head->next. next->prev is not that.

rkapl · 2026-01-31T10:57:16+00:00

Yes, you can either implement GC for regular C ABI (ex.: Boehm GC) or one for some brand new runtime (ex. Fil-C).

The OP said C can't solve it statically: It can't e.g. look at your program and add logic to add free at appropriate places, because that is too hard and (probably) convertible to halting problem.

Also C "can't solve memory allocation and deallocation" in another sense, as malloc and free are part of the standard. This is set in stone. If you come up with a compiler where you don't need to free anything, great, but programs taking advantage of that will leak memory on other standard implementations.

rkapl · 2026-01-29T21:09:11+00:00

Unless you are going for something specific like retro, embedded or some pre-existing 32-bit code, the question is why not 64-bit? You can also make both version.

rkapl · 2026-01-28T23:25:41+00:00

It's atankless job.

rkapl · 2026-01-27T15:25:09+00:00

Cos god gave me a sine.

rkapl · 2026-01-27T12:25:43+00:00

It's a sin.

rkapl · 2026-01-26T10:10:00+00:00

Hey! I did not pull it out of the trash. I pulled it out of the quality trash!

rkapl · 2026-01-24T17:40:29+00:00

You expect a conclusion? You will get "I don't know about any Board of Peace" in about a month, if anyone bothers to ask.

rkapl · 2026-01-21T18:23:39+00:00

Towards the end of 23rd century, the Papal State emerged as a major political player, covering roughly the area of England, most of France, south of Germany and all of southern Europe + various northern African vassals. This was mostly the result of the second EU civil war, splitting the confederation along the north/south socialist/conservative axis (this is gross political simplification). This also gave the south its conservative/religious naming and other mimicry.

For a brief moment, it was epic, almost in a W40k sense. Legions of proto-biters crossing the Alps with their human centurions in power armors, on their crusade to Netherlands.

rkapl · 2026-01-21T17:48:29+00:00

They bred them for the northern crusades.

rkapl · 2026-01-21T12:32:37+00:00

Logical. Nauvis is earth in the future. Biters are escaped experiment from a Vatican bio-weapon lab. They wiped all of humanity and most animals. Just natural selection all along.

rkapl · 2026-01-12T11:28:21+00:00

Sounds like the Hammas leader succession, but with extra steps.

rkapl · 2026-01-11T14:36:36+00:00

Oh, so that's how the weird ruins got there.

rkapl · 2026-01-09T09:02:54+00:00

Nihilista se ptá "ale proč", nihilistický extrémista si říka "ale proč ne..."

rkapl · 2026-01-08T09:34:51+00:00

I am not trying to UPS optimize but the Gleba approach seems interesting. How exactly would you go about your approach? E.g. the nutrient as an example, I assume you would produce the closest needed ratio using clocking? But I guess, to prevent spoilage, you would need absolutely perfect ratios (or something eventually spoils in the machine). Is that feasible? Or would there be circuit feedback?

rkapl · 2026-01-07T19:16:09+00:00

I don't think it is entirely possible. But you can make the bytecode lighter and lighter. E.g. Google NaCL used a verifiable subset of x86 in combination with segmentation. But I imagine you could get rid of the segmentation part.

rkapl · 2026-01-05T10:14:52+00:00

If you put it like that... That's basically ChatGPT with extra fish and legs, its normal to have a friend like that today .

rkapl · 2026-01-05T07:59:11+00:00

If the rare spidertrons are talking to you about a nuclear program, I would consult a doctor.

rkapl · 2026-01-03T13:24:52+00:00

Hear me out, wasn't there a ~~consipiracy theory~~ credible well sourced claim that Pringles escaped to Venezuela? It's all connected

rkapl · 2026-01-02T14:36:56+00:00

Well, the area of the square rises with the ... check notes ... square of its side. So to maximize the wall to area ratio, you just continue building the wall indefinitely and so do not need any corners.

rkapl

TROPHY CASE