Orlando Llanes @steadfastcoder

Indie Game Developer | Coder github.com/orlandol/ inveniam viam aut faciam Joined June 2020

Tweets

3K
Followers

163
Following

3K
Likes

11K

Mohit Mishra @chessMan786

4 days ago

This is the part 7 of Everything About Memory Allocators and next one will be the last part of this series. Let me know whether you liked this kind of series and what more do you expect. x.com/i/article/2104…

1 10 121 6K 144

View Details

Art world @Aartworlld

5 days ago

5 54 649 115K 108

View Details

Mohit Mishra @chessMan786

6 days ago

This is the part 6 of Everything About Memory Allocators. 2 more parts are left on this, so enjoy this read till then ;-) x.com/i/article/2102…

1 12 100 4K 73

View Details

Mohit Mishra @chessMan786

a week ago

This is the Part 5 of Everything About Memory Allocators x.com/i/article/2102…

1 12 92 3K 97

View Details

trish @TrisH0x2A

6 days ago

@spencercmd github.com/cs341-illinois…

4 13 141 6K 250

View Details

trish @TrisH0x2A

6 days ago

a professor at Illinois got frustrated with existing systems programming textbooks so he started a Wikibook with students helping write it it covers C, processes, threads, memory, networking, filesystems, scheduling, and security all in one free book

17 203 2K 49K 2K

View Details

Mohit Mishra @chessMan786

6 days ago

Virtual memory and the 4-level page walk Your program has never seen a real memory address. Every pointer is virtual, and the CPU translates it on every load and store. On x86_64 that translation is a 4 level table walk. Here is how it works.

1 5 72 3K 49

View Details

Orlando Llanes @steadfastcoder

a week ago

7) I wonder how future me will solve these problems 😅

0 0 0 2 0

View Details

Orlando Llanes @steadfastcoder

a week ago

6) On that note, I also wish I could use a hash calculation to make a unique, independently reproducible, type ID. Same issue though - hash values can collide when the input is larger than the value. Even two characters can collide, but wider input generally collides.

1 0 0 2 0

View Details

Orlando Llanes @steadfastcoder

a week ago

1) Started making a list of the functions I need for retg1, and entered the prototype declaration as well as functions. Still have a few to go, but they're like goals I can autopilot into.

1 0 0 15 0

View Details

Loisy @liovvan

a week ago

このワンコの顔、マジで笑う🤣 「お願い、ちょっとだけ唾飲ませて…息させて…」って顔してる😂🐶

4 3 50 28K 2

View Details

Mohit Mishra @chessMan786

a week ago

This is the part 4 for the Everything about Memory Allocators about Splitting and Coalescing. x.com/i/article/2102…

0 16 121 4K 116

View Details

Mohit Mishra @chessMan786

a week ago

Today's the day for Part 3 of Everything About Memory Allocators, and here we will see about calloc and realloc. In the next one, we will see about Splitting and Coalescing. Stay Tuned! x.com/i/article/2102…

0 16 141 4K 122

View Details

Orlando Llanes @steadfastcoder

2 weeks ago

7) All that said, I'm starting with the lexer, parser, symbol table and helpers; then I'll move on to the rest. I feel good about this iteration, which will end with a single file program retg1. c that can bootstrap and compile retg2. ret

0 0 0 7 0

View Details

Orlando Llanes @steadfastcoder

2 weeks ago

6c) On the command-line, it would be a prefix option: retg3 myprog. ret -dll mod1. ret -lib mod2. ret -obj mod3. ret which would build mod1. ret as mod1. dll; build mod2. ret as mod2. lib; build mod3. ret as mod3. obj; then import/link them to myprog. exe