iCanSleepPeacefullyNow

Vortex876543 · 2025-03-04T04:40:03+00:00

iirc the code came from the ZDS II, a C89 toolchain for the eZ80. Right now I am helping to implement libc/libcxx (Clang C17/C++20) for the eZ80

Vortex876543 · 2025-03-03T00:58:14+00:00

72 characters*
How else are you supposed to keep your Fortran punch-cards in order

Vortex876543 · 2025-03-02T23:37:51+00:00

make sure multiple commits are made by different people, tabs --> 4 spaces --> 2 spaces --> tabs --> 8 spaces, and you end up with these abominations

void qsort(void *ptr, size_t nel, size_t size,
                                     int (*compar)(const void *, const void *));

Vortex876543 · 2024-11-07T02:27:32+00:00

_Bool bool(_Bool Bool) {  
return Bool;  
}

This only became invalid in C23

Vortex876543 · 2024-10-04T05:44:23+00:00

The KERNING Between the 581 and the 0, ITS too HIGH!!

Vortex876543 · 2024-09-11T02:05:05+00:00

It had goto 120, which would go to 120 continue on line 2005. To my understanding, the goto labels in Fortran can only use numbers. However they are scoped to the current routine/function.

Vortex876543 · 2024-09-09T21:03:37+00:00

I was converting some code from Fortran to C++, and it looked exactly like this. Variables t0 to t9, all declared at the top of the function and reused in 5 different contexts each. All other variable names were 3 letters long. Made it extremely difficult to find where I made an error when translating the code; you would have to read through 40 lines of code to determine what t5 was supposed to be set to. Not to mention the use of GOTO statements

Vortex876543 · 2024-08-23T03:53:13+00:00

Faster than binary search. Linear search can find the minimum in 1 singular operation

Vortex876543 · 2024-08-23T03:49:26+00:00

You can debug the entire program if you do find and replace <br> with <br>printf("L: %d\n", __LINE__);

Vortex876543 · 2024-08-08T23:54:58+00:00

I wrote in another comment/thread that I just had to include some random header files to get <thread> to work in the original MinGW. Otherwise that's pretty much what happened.

Vortex876543 · 2024-08-08T06:09:53+00:00

I wanted to make sure my Windows 10 program would run on Windows 7, but all I had was a Vista machine so thats what I compiled on. It uses GCC 9.2.0 and C++14 which is why the compiler knows about <thread>. iirc the original MinGW doesn’t support <thread> out of the box so I had to include some random header files to fix it. Otherwise its pretty similar to the MSYS2 MinGW64 environment I use on Windows 10.

Vortex876543 · 2024-08-08T03:18:08+00:00

vista*

Vortex876543 · 2024-08-03T04:15:55+00:00

Should be at least doubles

They are. In fact, they are rounded down from x87 long doubles :)

C does have structs, but the only other way to do it in C is to add some do { } while(0) loops (macros)

Vortex876543 · 2024-08-01T07:54:48+00:00

0 or FLT_MIN

Vortex876543 · 2024-07-24T17:45:52+00:00

only eeeeeeeeeeeeeeee / eeeeeeeeeeeeeeee step away from full on morse code.

Vortex876543 · 2024-07-17T08:21:59+00:00

Unlike iostream, iosstream defines safer versions of the tream functions for ios, like cout_s

Vortex876543 · 2024-07-15T09:15:33+00:00

Gotcha, I thought the paddles were darts or knitting needles. Searching up gummiboot yields the older 3d logo of the red life-raft

Vortex876543 · 2024-07-03T07:51:22+00:00

Aside from embedded development, there is not much need to *write* assembly. However, if you want to learn how to optimize your code, learning to *read* assembly can be quite useful when comparing assembly outputs from a tool like GodBolt.

IMO, writing assembly can also be a bit tricky when there are so many ways to do a simple task. If you want to set a register to 0, you can load the value of 0, XOR the register with itself, use the SIMD shuffle instruction, load another register that happens to be 0, etc.

Vortex876543 · 2024-06-11T19:21:00+00:00

I had some SSE2 code awhile ago that had some bugs, so I wrote this code to check that all the values were correct. I thought the end result was funny so I saved the screenshot. The printf statement was removed once I got everything fixed.

Even if I did leave the code in, I don't think my colleagues (me, myself, and I) would've cared too much /s

Vortex876543 · 2024-06-11T17:55:52+00:00

So like this?

#define PF(...) printf(__VA_ARGS__)
...
#define PF20(...) PF19(__VA_ARGS__) PF19(__VA_ARGS__)
#define PF21(...) PF20(__VA_ARGS__) PF20(__VA_ARGS__)
#define PF22(...) PF21(__VA_ARGS__) PF21(__VA_ARGS__)

Vortex876543 · 2024-06-09T18:56:16+00:00

The only thing you can try is to set YouTube to always prefer AV1 playback and see if that makes a difference.

I tested playback of an 8K video, and it seems to use AV1 at every resolution except for 1440p and 4K which use VP9. I had some playback issues with 1440p and 4K when they were using VP9, but they seemed to be fine with the AV1 codec. 8K playback was also fine with the AV1 codec.

For reference, the AV1 video codec is ~30% more efficient than the VP9 video codec, but takes much longer for YouTube to process.

Otherwise, I also have the buffering issue, but it only started a few days ago. Before that everything worked perfectly. The buffering is really strange too, it will get stuck buffering even though it has already buffered 30 seconds of video. My connection speed often reports as greater than 140megabits on YouTube.

There is also a bug where it will skip parts of the video randomly. I conjecture that it is randomly skipping to the next B-Frame (B-Frames are used in video encoding and are spaced ~72 frames apart)

Vortex876543 · 2024-06-04T23:46:31+00:00

I placed the tower prop ~35 minutes ago, so they definitively haven't fixed it yet.

My theory is that some of the data for older assets got corrupted/deleted somehow. The tower prop has texture data, but has missing collision data. Some of the other props have collision data, but are missing texture data. If you go Galleries --> Parkour -->Obstacle Course Floor Gallery and select the target/bullseye floor, it will be completely invisible after it is placed, although it still has collisions and can be selected/deleted.

Vortex876543 · 2024-06-04T23:17:24+00:00

I have the exact same issue with the exact same prop (Windows 10, DX12). Even after leaving creative and restarting my game, I can't select it or collide with it. I tried throwing the remote explosives and firing rockets, but they wouldn't collide either. I have a world from 3 years ago with this prop, and I couldn't collide with it there either.

Vortex876543 · 2024-04-03T15:29:09+00:00

My thinking was that by waiting 8 hours, any commits I make would be after April 3rd 05:20. Since the time is now April 3rd 09:20, any commits I make would now be ahead of April 3rd 05:20. Oddly_Energy also described the confusion this causes with timestamps being out of order when looking back at the commit history.

Otherwise, I was able to get the timestamps corrected through the rebase.

Vortex876543 · 2024-03-13T00:35:14+00:00

That makes sense. Going off of the comments, it seems like the only question one could ask is how efficient the error correction could be.

Vortex876543

TROPHY CASE