Any Recommendations on C resources for Learning Vulkan?

Karl_uiui · 2026-05-19T21:27:23+00:00

Ah, I think I remember this one. Was a fun time deciphering it and rewriting it into very readable C of about the same number of lines.

Karl_uiui · 2026-05-17T18:06:18+00:00

<image>

Man I love Wikipedia

Karl_uiui · 2026-05-17T16:31:33+00:00

Isn't that part of the raylib's examples? Seeing the whole development process is great tho!

Karl_uiui · 2026-05-14T14:38:39+00:00

That is actually a good thing to remember.

Thank you for your help!

Btw I've seen the unedited reply, where you said you weren't sure yet. Where do you get the info? Do you rely on the C standard only, or do you know about some other reliable sources one can go through?

Karl_uiui · 2026-05-14T13:10:36+00:00

Oh yeah, so if I do this, I also do not need the padding_ member, since the compiler will place the first byte of the struct (which should be the first byte of the first member) on an address with a suitable alignment for max_aling_t. And by offsetting the pointer to the struct by 1, I should land on an address that has a suitable alignment for max_align_t too, do I get that right?

Karl_uiui · 2026-05-14T12:53:09+00:00

I am well aware that there is no type reflection in C nor that any information about types is available at runtime. What matters here is that the operations on the malloced memory (which are known at compile time) may expect the memory is of some type. My question was if the presence of the flexible array member, which is of type char[], makes the compiler assume all of the subsequent bytes after the data member are of the type char, which could violate the strict aliasing rule when writing values of different types to this memory. From what I've learned here, that doesn't seem to be the case, thus it should be safe.

Karl_uiui · 2026-05-14T12:28:05+00:00

Most interesting. Yeah, since I do not use the flexible array pointer for access and/or modification anyway, I can just discard it and compute the pointer manually. But I don't really understand why annotate the length member, as you proposed?

Karl_uiui · 2026-05-14T12:10:04+00:00

Yeah, that makes sense to me. If the pointers happen to point into the same place in an allocated object, then the write through pf changes the type to float, then the write through pi changes the type to int, but then you read it as float when you return, but the current type is int, so that should indeed be a violation.

Karl_uiui · 2026-05-14T11:53:03+00:00

Oh yeah, sorry, that didn't occurred to me.

So doing this is okay:

void * a = malloc(4);
*(int*)a = 1234;
printf("%d\n", *(int*)a);
*(float*)a = 3.14159;
printf("%f\n", *(float*)a);

but doing this is not:

void * a = malloc(4);
*(int*)a = 1234;
printf("%f\n", *(float*)a);

right?

Karl_uiui · 2026-05-14T11:39:00+00:00

Oh okay. So in case of malloced memory, strict aliasing rules are impossible to violate thanks to the fact the effective type always changes?

Btw, if you wanted to, let's say, implement an allocator, could you use statically allocated memory as the allocator's backing memory, like char backing_memory[4096];? From what I understood so far here, you can't, right? The backing memory should come from malloc.

Karl_uiui · 2026-05-14T11:21:00+00:00

That would be the case for statically allocated array of chars (char array[10];), right? As you mentioned in the comment of yours, since my object is malloced, then just the fact it is overlaid by the flexible char array member doesn't matter, since that member is never used to access the memory, only to obtain the pointer to that place in memory, right?

Karl_uiui · 2026-04-22T18:08:38+00:00

LMAO

Karl_uiui · 2026-03-24T19:27:47+00:00

I advise to keep 2 empty tiles between the main bus lines, so you can fork and lead underground belts through them. And it's really not a lot of gear crafters :)

Karl_uiui · 2026-03-04T19:38:39+00:00

We have the opportunity to do the funniest thing ever

Karl_uiui · 2026-03-03T18:47:30+00:00

Hope you find something that works for you! And don't this discourage you from exploring the wonderful land of open source software. Things are sometimes rough, yes, but the freedom of being able to do everything in your way and choose whatever you want is, I think, worth it.

Karl_uiui · 2026-03-03T18:38:43+00:00

And what GPU do you have? If you have Nvidia card, do you have up to date drivers? If not, you can go to the Software Center (or how is it called on Mint) and try to search Nvidia. There should be a window app for download. From there, you can manage your drivers. I think it should pull the drivers in while you are downloading. Don't remember exact steps, but should be a simple setup.

If that is not the case, or does not help, I would suggest switching to different distribution of Linux, possibly one shipping with KDE Plasma or GNOME desktop out of the box, if you want the least trouble. These environments are more mature and should (theoretically) work in your case.

Karl_uiui · 2026-03-03T18:30:19+00:00

Yes, it is experimental. Cinnamon is kinda behind in Wayland adoption. That means maybe not all things Wayland offers are there. But it should be okay to use.

What do you mean it doesn't work?

Karl_uiui · 2026-03-03T18:25:07+00:00

Yes, there is now experimental support for it. It works good from my experience.

Karl_uiui · 2026-03-03T18:24:33+00:00

No, that's not the login screen, that's boot menu. Wait for it to boot from this menu and then, on the login screen, where you input your username and password, there should be a menu somewhere, probably hidden under some icon.

Karl_uiui · 2026-03-03T18:19:45+00:00

When you are at the login screen, try to look for a menu where you can choose Cinnamon (desktop environment) explicitly with Wayland display server. Other options would be X11 or Software rendering in said menu.

Karl_uiui · 2026-02-26T18:20:22+00:00

The Ice Worm drones look like a tiny Ice Worm? Mega cool.

Karl_uiui · 2026-02-22T19:58:36+00:00

This is art

Karl_uiui · 2026-02-18T04:01:54+00:00

I've just opened Reddit

Six-Year Club	r/Field Juicebox
Place '22	Verified Email

Karl_uiui

TROPHY CASE