open-watcom-v2
gcc
open-watcom-v2 | gcc | |
---|---|---|
23 | 82 | |
921 | 8,746 | |
2.6% | 1.3% | |
9.9 | 9.9 | |
1 day ago | 5 days ago | |
C | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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.
open-watcom-v2
-
Djgpp
https://github.com/open-watcom/open-watcom-v2
In terms of ISO-complianceness, perhaps don't expect much. It basically C89 (the C99 support is still incomplete), and for C++... most likely not even C++98 - compliant.
-
Popularity of DOS/4GW made Win95 game compat easier, but with higher stakes
> You will also want to start with a 16-bit C compiler like Borland Turbo C or Microsoft C
The parent post mentioned they're going to use OpenWatcom which is an actively developed[0] C and C++ compiler that targets 16bit DOS (among others).
[0] https://github.com/open-watcom/open-watcom-v2
-
#pragma once / header guards / C++ committee.
Despite the lack of feature support, the compiler is still updated to this day, and still does support DOS, Windows, Linux, and OS/2, so it's modern in the sense of maintenance, just not really standards support. If you got further questions, I can send you the Discord link. They are pretty friendly.
-
Rust is Boring
My advice is, when you feel you need that challenge, install DOSBox or DOSBox-X and Open Watcom C/C++, DJGPP, or gcc-ia16 and do some retro-programming. You'll also get the fun of being able to do low-level hardware twiddling and rely on DOS being so simple that it's effectively an RTOS.
-
Build C/C++ programs to run on homebrew 286?
If you want to build under Linux, I would recommend you look at Open Watcom. It's the best open source 16-bit x86 C compiler, IMHO.
-
"My Reaction to Dr. Stroustrup’s Recent Memory Safety Comments"
I have recently found out that Watcom C still exists. And not just exists, but there are plenty of commits.
-
Win16 Retro Development
I should note, that OpenWatcom 2.0[1] is far better for supporting more recent C and C++ code, modern hosts and tooling, but still able to compile into 16 bit code. It is also actively maintained. Instead of MASM I recommend JWasm[2] + Jwlink[3]. Back in time I did a fork[4] of JWasm that has cleaner build system (CMake).
[1] https://github.com/open-watcom/open-watcom-v2
[2] https://github.com/Baron-von-Riedesel/JWasm
[3] https://github.com/JWasm/JWlink
[4] https://github.com/JWasm/JWasm
-
Rendering like it's 1996 - Baby's first pixel
If you want to run this in DOS: the code under src/should actually compile with this OpenWatcom fork via the -za99 flag. MiniFB however will not compile. You'd have to palettize the output pixel buffer to 256 colors and then blit it to 0xa000if you fancy that.
-
Falsehoods programmers believe about undefined behavior
GCC, clang or maybe watcom? You wouldn't find it there (before invention of AGI, but that would be entirely different can of worms).
- Having trouble setting up whonix on Mac OS
gcc
-
GCC 14.1 Release
Upd: searching in the github mirror by the commit hash from the issue, found that https://github.com/gcc-mirror/gcc/commit/1e3312a25a7b34d6e3f... is in fact in the 'releases/gcc-14.1.0' tag.
Even weirder that this one got swept under the changelog rug, it's a pretty major issue.
-
C++ Safety, in Context
> It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.
Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.
Case in point, this was fixed in both major C++ libraries:
https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...
https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...
So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?
- Std: Clamp generates less efficient assembly than std:min(max,std:max(min,v))
-
Converting the Kernel to C++
Somewhat related: In 2020 gcc bumped the requirement for bootstrapping to be a C++11 compiler [0]. Would have been fun to see the kernel finally adopt C++14 as the author suggested.
I don't think that Linus will allow this since he just commented that he will allow rust in drivers and major subsystems [1].
I do found it pretty funny that even Linus is also not writing any rust code, but is reading rust code.
I would have hoped see more answers or see something in here from actual kernel developers.
0: https://github.com/gcc-mirror/gcc/commit/5329b59a2e13dabbe20...
-
Understanding Objective-C by transpiling it to C++
> They’re saying that a lot of the restrictions makes things much harder than other languages. Hence the general problem rust has where a lot of trivial tasks in other languages are extremely challenging.
Like what? So far the discussion has revolved around rewriting a linked list, which people generally shouldn't ever need to do because it's included in the standard lib for most languages. And it's a decidedly nontrivial task to do as well as the standard lib when you don't sacrifice runtime overhead to be able to handwave object lifecycle management.
- C++: https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-...
- Rust: https://doc.rust-lang.org/beta/src/alloc/collections/linked_...
> No need to get defensive, no one is arguing that rust doesn’t do a lot of things well.
That's literally what bsaul is arguing in another comment. :)
> You’re talking up getting a safe implementation in C, but what matters is “can I get the same level of safety with less complexity in any language”, and the answer is yes: Java and c# implementations of a thread safe linked list are trivial.
Less perceived complexity. In Java and C# you're delegating the responsibility of lifecycle management to garbage collectors. For small to medium scale web apps, the added complexity will be under the hood and you won't have to worry about it. For extreme use cases, the behavior and overhead of the garbage collector does became relevant.
If you factor in the code for the garbage collector that Java and C# depend on, the code complexity will tilt dramatically in favor of C++ or Rust.
However, it's going to be non-idiomatic to rewrite a garbage collector in Java or C# like it is to rewrite a linked list in Rust. If we consider the languages as they're actually used, rather than an academic scenario which mostly crops up when people expect the language to behave like C or Java, the comparison is a lot more favorable than you're framing it as.
> If I wanted I could do it in c++ though the complexity would be more than c# and Java it would be easier than rust.
You can certainly write a thread-safe linked list in C++, but then the enforcement of any assumptions you made about using it will be a manual burden on the user. This isn't just a design problem you can solve with more code - C++ is incapable of expressing the same restrictions as Rust, because doing so would break compatibility with C++ code and the language constructs needed to do so don't exist.
So it's somewhat apples and oranges here. Yes, you may have provided your team with a linked list, but it will either
-
Committing to Rust for Kernel Code
GCC is also written in C++, and has had C++ deps since 2013:
https://github.com/gcc-mirror/gcc/blob/master/gcc/c/c-parser...
- Spitbol 360: an implementation of SNOBOL4 for IBM 360 compatible computers
-
are most computer programming languages public domain, or do their creators get a say in what you do with them?
Compliers/Interpreters are also very commonly open source (here is the source code for a popular C compiler). That means you can even modify the compiler's code and change its behavior if you wanted to.
- Learn to write production quality STL like classes
-
Which compiler is conforming here?
according to this commit, the story here seems to be much more interessting than I initially anticipated.
What are some alternatives?
gcc-ia16 - Fork of Lambertsen & Jenner (& al.)'s IA-16 (Intel 16-bit x86) port of GNU compilers ― added far pointers & more • use https://github.com/tkchia/build-ia16 to build • Ubuntu binaries at https://launchpad.net/%7Etkchia/+archive/ubuntu/build-ia16/ • DJGPP/MS-DOS binaries at https://gitlab.com/tkchia/build-ia16/-/releases • mirror of https://gitlab.com/tkchia/gcc-ia16
CMake - Mirror of CMake upstream repository
DOOM - DOOM Open Source Release
rtl8192eu-linux-driver - Drivers for the rtl8192eu chipset for wireless adapters (D-Link DWA-131 rev E1 included!)
MS-DOS - The original sources of MS-DOS 1.25 and 2.0, for reference purposes
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
em-dosbox - An Emscripten port of DOSBox
STL - MSVC's implementation of the C++ Standard Library.
abrash-black-book - Markdown source for Michael Abrash's Graphics Programming Black Book
cobol-on-wheelchair - Micro web-framework for COBOL
emu2 - Simple x86 and DOS emulator for the Linux terminal.
busybox - The Swiss Army Knife of Embedded Linux - private tree