Which compiler is the best?
Which compiler will be the dominant one in the near future?
Compilers
gcc
gcc
clang is only good if your boss is requiring you to cuck the developers.
I'm quite impressed with the turnaround gcc made. I thought the whole thing was doomed back during the egcs/pgcc days. I guess technically it actually was doomed as the egcs guys took over.
holyc
Don't be a nigger cattle, holyc is the only compiler that you ever need.
The best compiler will be the compiler which is the most capable. The dominant compiler will be the one that is most dominant.
compcert
gcc/clang will remain
...
Did you even read the rest?
I read it's formally verified by someone's cock to produce embarrassingly shitty output slower than a compiler from before many anons were born.
clang is open source and optimizes better than gcc
and gcc isn't?
Are you literally retarded? gcc is Free Software.
Open Sores != Free Software
gnu.org
I don't think you understand the number of P1/P2 bugs gcc has every release. Being able to produce good code and being sure of it is extra important.
Clang and GCC are both open source as well as free software.
The page you linked says "The two terms describe almost the same category of software".
You're missing the point of the way open source misses the point. Educate yourself, for example by carefully reading the page you linked, because you're not providing any arguments against clang.
If you want a gnu.org page to link to to protest clang, try this one:
gnu.org
Free software and copyleft are different things.
...
(((intel))) compiler because it has the best (((x86))) optimization
clang. Companies love cuck licensed open sores software and are afraid of free software.
gcc is not open source
if I use even a small fragment of it in my private project I will be forced to release all my code on the same communism infected license
Kill yourself, retard.
(checked)
not an argument
Good. Stop being a CIAnigger.
Also, if this is shit that only you will be using, privately, you don't have to release the source.
anyone who knows can force me to release it, so i can't tell anyone that i am using it and disconnect internet just in case
Do any companies develop in-house additions to clang btw? If the snowflake license on it allows.
Only if they get a copy of your software. As long as you don't share the software itself nobody can demand anything from you.
The Open Watcom license does require you to publish your source code even for people who don't already have a copy of the software, which is why the FSF considers the Open Watcom license proprietary.
I am still forced to do something instead of posibility to do it freely
And as a producer with a goal to make money, I don't know why one would ever consider GNU. It also prohibits you from selling to any of the various walled gardens, which people clearly enjoy. (Apple, Google stores etc.)
Will they ever learn?
**Permissive = anarkiddies (goal: personal freedom)
Copyleft = fascism/natsoc (goal: group's freedom)**
Good idea. We need race and ideology specific licences.
they already exist rust-lang.org
no, and even if they did they could do inhouse gcc extensions too without having to release them. companies are scared of the evil "viral" copyleft boogeyman.
gcc
cucklang
Depends. Clang has some advantages (compiles faster, is much easier to extend, license). But so does gcc (works on anything, license). Which produces better code depends, I've seen huge differences between the two for both sides (usually, but not always, icc > gcc > clang). Very long-term clang has the advantage since their code is less fucked because it's more recent.
You only need to release the code to your users. Since the project is private you have few users and can add in the contract they can't develop a competing software.
You don't always need maximum speed. Often you only need "does x before y seconds pass". Take the guidance software for a rocket for instance. You can afford wasting a few more watts to avoid some crazy bug.
If I require reliability I'd already be solving the problem with three different builds of the program where the output is compared so I could detect and recover from program errors, tool errors, random errors, hardware faults, physical damage (combat aircraft), cosmic rays, etc.. A slow as shit "formally proved" language is of little value since I'm not going to be putting all my eggs in one basket.
Compiler for what?
Webasm.
of programming language
What is this?
Except it doesn't, you lying fuck. The Clang fuckers kept crying about its lower compile times, and now it can't do that either.
Kindly hang yourself.
...
...
The one you write yourself, nigger