DOOM
freebsd-src
Our great sponsors
DOOM | freebsd-src | |
---|---|---|
91 | 133 | |
12,687 | 7,461 | |
2.8% | 1.4% | |
2.5 | 10.0 | |
8 days ago | 5 days ago | |
C++ | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
DOOM
-
Doom Released Under GPLv2
commercially exploit or use for any commercial purpose."
[1] https://github.com/id-Software/DOOM/commit/4eb368a960647c8cc...
-
GTA 5 source code leaks online
The original Doom had third-party audio playback routines, so the source came with a rewritten sound server: https://github.com/id-Software/DOOM/tree/master/sndserv
The bad news: this code only compiles and runs on linux. We couldn't
- What you can do with C ?
-
Software Disenchantment
Here's a repo for you with no test coverage and no auto-generated DI. They using unsafe pointers all over the place, too!
https://github.com/id-Software/DOOM
Shall I prepare the postage for the letter in which you'll call John Carmack an MBA? Should we send another to Chris Sawyer? I heard he didn't even write a formal design doc for Roller Coaster Tycoon!
-
Ask HN: Good practices for my first C project
cURL is one of the most used C libs and is an example of good quality C code. If you follow the style used there, see e.g. https://github.com/curl/curl/blob/master/lib/dynhds.h (and associated dynhds.c) you will be good.
Looking at the source of some of the old game-engines from the era that have since been released as open-source can also be helpful, like https://github.com/id-Software/DOOM.
In both cases notice how simple and elegant a lot of the code is. There is already enough complexity inherent in the problem they are solving, and that is where the focus should be.
Any IDE with a working language server to make it easy to jump around and refactor should work fine. Limitations might be due to the C language itself?
Error handling on such a fixed platform does not need to be super-advanced. You should always be within the confines of the system so there shouldn't be much that can go wrong. If stuff goes wrong anyway just being able call a function Fatal("FooBar failed with code 34") when unexpected stuff happens and have it log somewhere to be able to dig around should be enough. You never need to be able to recover and retry.
Make sure to use https://clang.llvm.org/docs/AddressSanitizer.html or a similar tool when developing outside of the PSOne.
That said, consider statically allocating global buffers for most stuff and avoid using the heap for most stuff.
Good luck working within the confines of the PSOne! Many hackers have pulled the hair from their head on that platform ;)
- Ask HN: Where do I find good code to read?
-
Running Stable Diffusion in 260MB of RAM
Probably more easily than you'd think. DOOM is open source[1], and as GP alludes, is probably the most frequently ported game in existence, so its source code almost certainly appears multiple times in GPT-4's training set, likely alongside multiple annotated explanations.
[1] https://github.com/id-Software/DOOM
- Where can I get game files to study?
-
Some were meant for C [pdf]
I'd define an arena as the pattern where the arena itself owns N objects. So you free the arena to free all objects.
My first job was at EA working on console games (PS2, GameCube, XBox, no OS or virtual memory on any of them), and while at the time I was too junior to touch the memory allocators themselves, we were definitely not malloc-ing and freeing all the time.
It was more like you load data for the level in one stage, which creates a ton of data structures, and then you enter a loop to draw every frame quickly. There were many global variables.
---
Wikipedia calls it a region, zone, arena, area, or memory context, and that seems about right:
https://en.wikipedia.org/wiki/Region-based_memory_management
It describes history from 1967 (before C was invented!) and has some good examples from Apache ("pools") and Postgres ("memory contexts").
I also just looked at these codebases:
https://github.com/mit-pdos/xv6-public (based on code from the 70's)
https://github.com/id-Software/DOOM (1997)
I looked at allocproc() in xv6, and gives you an object from a fixed global array. A lot of C code in the 80's and 90's was essentially "kernel code" in that it didn't have an OS underneath it. Embedded systems didn't run on full-fledges OSes.
DOOM tends to use a lot of what I would call "pools" -- arrays of objects of a fixed size, and that's basically what I remember from EA.
Though in g_game.c, there is definitely an arena of size 0x20000 called "demobuffer". It's used with a bump allocator.
---
So I'd say
- malloc / free of individual objects was NEVER what C code looked like (aside from toy code in college)
- arena allocators were used, but global vars and pools are also very common.
- arenas are more or less wash for memory safety. they help you in some ways, but hurt you in others.
The reason C programmers don't malloc/free all the time is for speed, not memory safety. Arenas are still unsafe.
When you free an arena, you have no guarantee there's nothing that points to it anymore.
Also, something that shouldn't be underestimated is that arena allocators break tools like ASAN, which use the malloc() free() interface. This was underscored to me by writing a garbage collector -- the custom allocator "broke" ASAN, and that was actually a problem:
https://www.oilshell.org/blog/2023/01/garbage-collector.html
If you want memory safety in your C code, you should be using ASAN (dynamically instrumented allocators) and good test coverage. Arenas don't help -- they can actually hurt. An arena is a trivial idea -- the problem is more if that usage pattern actually matches your application, and apps evolve over time.
-
What is your gender?
Doom
freebsd-src
- You shouldn't run a BSD on a PC
- Linux Crisis Tools
- What about the vfs.zfs.bclone_enabled sysctl now?
-
Personal FreeBSD PKGBASE Update Server
2023-06-26: https://github.com/freebsd/freebsd-src/commit/ee0aa1ce12b3caea34477a31e9d2111a329e33b9 to main (tagged release/14.0.0).
- What version of ZFS at FreeBSD solves the block cloning issue?
-
Installing FreeBSD 14 Stable on an T480 Laptop w/ an Encrypted Home Directory
It's not yet in FreeBSD base so if you want to test it you'll have to use the patch from the PR: https://github.com/freebsd/freebsd-src/pull/881
-
FreeBSD 14.0 Delivering Great Performance Uplift
Lots of great work by many people. But I bet this guy and his optimizations to the vfs and locking has made a significant impact.
https://github.com/freebsd/freebsd-src/commits?author=mjguzi...
-
ZFS 2.2.1: Block Cloning disabled due to data corruption
and then there were deep concerns about the stability of same, so vfs.zfs.bclone_enabled = 0 was left in-place
https://github.com/freebsd/freebsd-src/commit/068913e4ba3dd9...
-
FreeBSD 14.0-Release Announcement
Well there are some examples:
https://github.com/freebsd/freebsd-src/tree/main/share/examp...
But yeah that pf.conf could be expanded allot, but there are many source to cobble a conf together. My conf is massive but 99.9% commented out so i have my "template" for nearly everything, from mail to web to blacklistd etc.
-
Git cherry-pick and revert use 3-way merge
The BSD version is sort of very recent, for what it's worth -- FreeBSD imported a not fully functional version in 2017 and has seen more work on it in 2022: https://github.com/freebsd/freebsd-src/commits/main/usr.bin/... , but the default version shipped is still GNU diff3: https://man.freebsd.org/cgi/man.cgi?query=diff3&apropos=0&se... .
What are some alternatives?
open-watcom-v2 - Open Watcom V2.0 - Source code repository, Wiki, Latest Binary build, Archived builds including all installers for download.
podman - Podman: A tool for managing OCI containers and pods.
project-based-tutorials-in-c - A curated list of project-based tutorials in C
musl - unofficial musl mirror git://git.musl-libc.org/musl
Apollo-11 - Original Apollo 11 Guidance Computer (AGC) source code for the command and lunar modules.
darwin-xnu - Legacy mirror of Darwin Kernel. Replaced by https://github.com/apple-oss-distributions/xnu
doomgeneric - Easily portable doom
src - Read-only git conversion of OpenBSD's official CVS src repository. Pull requests not accepted - send diffs to the tech@ mailing list.
luxtorpeda - Steam Play compatibility tool to run games using native Linux engines
coreutils - upstream mirror
angband - A free, single-player roguelike dungeon exploration game
ravynos - A BSD-based OS project that aims to provide source and binary compatibility with macOSĀ® and a similar user experience.