13 ms·
Why people were enthused about GCC early on in its life
- timclark 12y agoSun removing the C compiler from Solaris pretty much made it obligatory for my whole university department to install GCC in the early 90s.
- simonh 12y agoAnd if you're using a cross-platform compiler, you've no longer got any need for a particular OS to run your software on. And now there are thousands of university students and professors relying on gcc, and therefore willing to devote time and effort to improve it. And oh look - this Finnish kid has just released an open source Unix clone than runs gcc compiled software just fine, and it's free too! I can't really say that this decission killed sun. I don't knoe how much revenue they got from selling cc, and they were probably toast anyway in the long run. Their main selling point was that they were the same as all the other versions of Unix.
- ska 12y agoIt's the hardware costs that killed the unix vendors relative to commodity beige boxes, not the software Linux (and to some degree the BSD's) just gave a smoother path. I recall seeing side by side memory quotes from Intel (i.e. an "expensive" vendor in the space, when they were shipping servers) and SGI for the same amount of memory on smallish servers - from memory the SGI was about $18k vs $500 for the intel. Staring at that difference it becomes pretty hard to justify, even if the memory bus was much better. I could buy a couple of new servers for the cost of that memory upgrade. I suspect Sun's pulling the free c compiler was just one of many "cost cutting" (which end up being revenue cutting) decisions made by a company that saw the writing on the wall but couldn't see how to avoid it.
- yuhong 12y agoThe other thread mentions that they provided the first unbundled C compiler back in 1989, closer to the standardization of ANSI C, which is probably no coincidence as many compilers had to be revised to support it and another reason why GCC became popular. It was not until they moved to SVR4 with Solaris that they removed the bundled one however, after gcc 2.0 was released I think.
- bluedino 12y agoThat's why both Sun and SGI made last-ditch efforts to run on Intel hardware towards the end of their server/workstation production. But that made it worse, they were selling x86 hardware for much higher prices than HP or Dell, without much advantage.
- acveilleux 12y agoThe sun C compiler was pulled in an era where the Unix workstations were (1) very clearly superior to PCs and (2) available with steep .edu discounts. By 2000, the Unix workstation were not much faster outside of 3D hardware and floating points and the discounted price was well above the "equivalent" PC costs. By 2005, the PCs had exceeded Unix workstations in every way. The line is kinda blurry in my head but basically a 2004 vintage AMD CPU could do in software (using MesaGL) roughly the same OpenGL performance as a '98 vintage O2 could do with a decent frame buffer. Once the nVidia drivers became ubiquitous, that PC ran circle around all of our SGIs except for the Octane2s (at a 10:1 price differential.) By 2006, we were down to a single Octane2 with a busted frame buffer being kept to avoid relicensing a numerical package for $$$$.
- ska 12y agoI want to say my quote comparison came from '96, but I could be off a bit. At any rate, the unix vendors still all had pretty significant hardware advantages over even the beefiest PC ... but the bang/buck was already pretty painful. We had systems developed on Sun, but we couldn't afford to deploy them on Sun hardware. After briefly flirting with the idea that SunOS x86 would be a viable path, we gave up and moved to linux on commodity hardware. It was a new enough thing to do (in the market we were in) that we got a few raised eyebrows, but it turned out to be the right decision.
- acveilleux 12y agoYep, without .edu discount, by the time the P-Pro (mid/late 90s) came out the value proposition was really bad. For integer performance RISC had no benefits left by 1996-1997. 300Mhz P2 (in a Compaq workstation) was at parity with a 250Mhz R10k (SGI O2). The P2 as a fully assembled system was priced less than the R10k CPU alone. Only the huge amount of cash available to dot-coms propped up Sun then. With all the "you need sun servers for dot-coms" beliefs. My current employer made the same call (Linux on commodity PC) around the same time for the same reasons. It took ~8-10 years for competitors to stop using the fact it was Linux based for FUD. Now the only issue we get is Windows-only shop (very common in our industry) complaining that we're the only non-Windows system they use.
- pjmlp 12y agoIf BSD and Linux hadn't happened, Windows NT line would have taken all workstations market.
- VLM 12y agoPerhaps. Having been there at the time, OS/2 was killed by linux. So... you're not going to run this new windows95 thing, eh? Then why bother running OS/2 when there's linux?
- pjmlp 12y agoBack then I remeber reading articles all the time about UNIX vs Windows NT. OS/2 wasn't really a thing, at least not in Portugal. PC able to run it confortably cost at least 500€ more than the ones that would fly with Windows 3.1. Sure it wasn't the same thing, but for the majority of the folks it was good enough for what they wanted a computer for. Actually I would say when Linux came to be a thing, OS/2 was already gone. I only saw OS/2 once live back in 1994 in the anual computer expo in Lisbon. GNU/Linux in 1995 still wasn't for the faint of heart. My Slackware 2.0 took quite some effort to install.
- kjs3 12y agoAlso having been there, my admittedly fading memory remembers OS/2 as doomed before Linux was really an function parity option. And OS/2 wasn't really put up as a alternative to Unix (certainly IBM didn't want to cannibalize AIX); rather it was the server OS and upgrade to Windows that Microsoft customers were screaming for. Microsoft effectively killed off OS/2 the day they said "forget about OS/2...what you really wan't is this nifty thing we've got cooking called NT", no matter the effort IBM continued to pour into it.
- yuhong 12y agoYea, but that is only part of the story. This fiasco ended up being so bad it used to be one of my favorite topics. "Microsoft Munchkins" and DR-DOS are two of the reasons why.
- 12y ago
- unwind 12y agoMaybe I'm weird, but I'm still enthused about GCC. I mean come on, it's a free high-quality C compiler for almost any platform you can dig up! That's just awesome! C hasn't died or gone away since the 1980s, and being able to compile C for such a wide range of processors and platforms is great, in my opinion.
- jordigh 12y ago> Maybe I'm weird, but I'm still enthused about GCC. I'm just as weird as you. I am hoping to be able to devote some time this year to cross-pollinate with David Malcolm's work to get libgccjit working on GNU Octave: https://savannah.gnu.org/patch/index.php?8395 https://savannah.gnu.org/patch/index.php?8395
- gerbilly 12y agoI'm weird too, and I'd add that I think Autoconf is also awesome.
- jordigh 12y agoI think the idea of autoconf is great (test for features, not for versions). The implementation in m4 is sadness. It's possible to do autoconf-style checks in other build systems, but not as easily. I don't know why most build systems seem to ignore the wisdom of autoconf.
- kevin_thibedeau 12y agom4 is actually pretty awesome when fulfilling its original purpose of adding macros to programming languages. Certainly it's not hygienic and is a pain to debug but it can work wonders to bypass language limitations especially when dealing with assembly code.
- lmm 12y agoLLVM seems to be where the interesting action is these days, I think mostly because it's adopted a superior modular design. GCC's technical design was compromised by RMS' desire to keep it tightly coupled for licensing reasons, and in the past few years the pain of that has really started to be fault. Which is somewhat ironic considering how the free software movement started.
- kokey 12y agoI do remember something about SGI making you pay extra for the C compiler for IRIX. Perhaps they only made it free for universities.
- abruzzi 12y agoYup, they used MIPSpro compiler but it cost extra. And my recollection was that gcc wasn't fully functional without MIPSpro installed.
- opk 12y agoYou didn't get the system include files without having the compiler so, yes, gcc wasn't a full solution. Also missing without paying extra was troff so I had to use groff just to be able to format man pages (they mostly came preformatted).
- randcraw 12y agoThat was not the case when I used Irix (commercially), or later when I worked at SGI. Perhaps you mean "Son of SGI", the company that once was Rackable Systems?
- spydum 12y agoSun did the same thing on Solaris (charging extra for the compiler).
- blumentopf 12y agoIt wasn't free for universities, but in the first half of the 90s, SGI offered so-called "Varsity" contracts, which was basically a campus license for OS updates and unbundled products like compilers, NFS/YP and the "Documenter's Workbench" (a fancy name for troff/nroff).
- rogerbinns 12y agoThere were other reasons too. I worked at a place where we ported our software to 20 different versions of Unix[1]! gcc tended to be a lot less buggy than vendor compilers, and what bugs there were tended to be across all platforms. gcc's error messages were also a lot better than vendor compilers, as were regular diagnostics. gcc -Wall was a huge boon to improving code quality. If you were doing C++ for cross platform software, then gcc was the only game in town. The vendor compilers were at different versions of the C++ spec, had different libc++, tended to crash a lot, and had really bad messages. Heck gcc even added a flag to generate warnings based on Scott Meyers' Effective C++ books. When the vendor compiler started being sold separately, they also included licensing daemons. Every invocation of the compiler would check with the licensing daemon to make sure you didn't go over your license limit. The license daemons also tended to crash or get confused, causing even more grief trying to compile a large code base. At the end of the day vendor compilers were unreliable, buggy, unpleasant and a pain to work with. gcc was developer friendly and worked well. That got a lot of enthusiasm. [1] You can get an idea of what development was like back then http://www.rogerbinns.com/visionfs.html http://www.rogerbinns.com/visionfs.html
- randcraw 12y agoIf I may add emphasis... GCC's error messages were a HUGE improvement over existing compilers. Back in 1985, C compilers might tell you what line the error was on, but they also might not. GCC went further, revealing not only the line number but added a carat pointing to the precise term in the source code that was the source of the error. This was a godsend. In addition GCC's error messages were human readable. Unlike Microsoft, whose compilers and interpreters had long produced only line numbers and error codes, GCC wrote their messages in English, which were sometimes tuned further to fit the syntax. At the time, all this was a really big advancement over non-IDE compilers (which then died a thousand deaths when the cfront translator and then OOP's general lugubriousness made error messages illegible once again).
- jdp23 12y agoVery true! It's easy to forget how bad things were back then ...
- chisleu 12y agoI'm still enthused about GCC!!! :) When I started using it, The alternatives were expensive. Even the educational version of Borland our university used was expensive (The mediocre book it came with was ~$300!!!) It isn't as performant or as well tested as professional compilers (that cost tens of thousands or more!) You wouldn't expect it to be, would you?
- jordigh 12y ago> You wouldn't expect it to be, would you? Yes I would, especially since it's often made by the same people (Intel, IBM, Google)... No reason to not keep improving gcc!
- chisleu 12y agoThere is no reason to expect a product with $100M spent in testing by some of the highest paid mathematics and software engineers in the world to keep up with free software? I say that is wrong. We should expect it to be better, and it is. The intel compiler is faster than GCC on Intel hardware and it always will be. Why? Because GCC can't keep up with the new hardware that comes out. Proprietary compilers have always had the upper hand because incredibly complicated optimizations are incredibly hard to reverse engineer.
- jordigh 12y ago> There is no reason to expect a product with $100M spent in testing by some of the highest paid mathematics and software engineers in the world to keep up with free software? Are you aware that gcc has probably just as much if not more money poured into it? It's not a product of a bunch of hobbyists. Most of the gcc code is done by contributors who are paid to work on gcc. A lot of it is done precisely by companies who are interested in gcc generating the right code for niche hardware.
- Alupis 12y ago> t isn't as performant or as well tested as professional compilers I don't know how true this statement is. ICC has been found to be very lacking compared to both gcc and clang -- and I'd wager in-house testing doesn't compare to massive world-wide deployment of gcc and clang as far as rooting out tough bugs that crop up in weird circumstances.
- 4k 12y agoWhere does the author establish that people are not enthused about gcc anymore? Or does he not even imply that?
- wampus 12y agoNo, he's providing an alternative reason for gcc's popularity in response to Rob Landley's email[1] that asserts that it was due to developers determined "to avoid paying Ed Zander extra for Sun's Solaris compiler." [1] http://article.gmane.org/gmane.linux.toybox/1890 http://article.gmane.org/gmane.linux.toybox/1890
- randcraw 12y agoThere's another big reason to still be 'enthused' by GCC: without GCC we wouldn't have Linux. Or Mozilla/Firefox. Or virtually all of the shareware / freeware we largely take for granted, that frees users and developers alike from the domination of control-freak juggernauts like Apple and Microsoft and Oracle. Every day I'm enthused by GCC and the freedoms it spawned.
- ploxiln 12y agoThat is a great point. ... and without Firefox, how painful would it have been to wrest control of the internet away from IE6? Would Apple have even had a chance, or would they be stuck with IE5.5 for Mac? What would they base Safari on, if there wasn't KHTML for KDE (which might not exist without gcc)? What if Apple couldn't make an independent phone / tablet with browser, would we all still be stuck with flash? No way to really know what would have happened, but it's a bit scary. (EDIT: I'm not a fan of Apple stuff due to their walled gardens, but I do recognize their role, along with Firefox, in saving us from an IE/flash internet and thus from a crazier Windows monoculture.)
- ptype 12y agoWe should be. It's amazing that it's available free (x2). I remember when my choice of programming language was determined by which compiler I could get hold of. So I ended up using Turbo Pascal. The local library had some C books but I couldn't find a compiler. (TP had an amazing IDE though for its time...)
- carlob 12y agoHonest question about grammar (not a native speaker): is enthused correct here? Other than the fact that enthuse is a verb that was made up from enthusiasm, shouldn't this be "Why people were enthusiastic about…", "Why people enthused about…" or "Why people were enthused by…"?
- omega_rythm 12y agoYes, it's correct, at least my dictionary says so.
- munificent 12y agoIt's correct. As an intransitive verb, the subject is the person feeling enthusiasm. "I'm enthused to be going to Disneyland!" As a transitive verb, the subject is the thing causing enthusiasm. "Disneyland enthuses me!" (This formation does tend to be less common.)
- carlob 12y agoDon't all verbs use have as the auxiliary in the present perfect tense? As such I am enthused would not be an intransitive verb, but either a nominal predicate or a passive verbal predicate. A correct intransitive form would be "I've enthused about going to Disneyland". In the first case enthused should be replaced by enthusiastic, which is the correct adjective, in the second case you would use by rather than about as a preposition for the agent. Correct?
- frandroid 12y agoYou'll just never find anyone using this verb in spoken English...
- Kaligule 12y agotldr: gcc was a good compiler compared with the existing alternatives, so people used it. It also was free.
- cbsmith 12y agoHonestly, GCC was a pretty good optimizing compiler even on RISC architectures. The one exception was on SPARC, because the optimizer didn't take advantage of the "register windows" feature, which arguably is the most un-RISCy aspect of the SPARC architecture. RISC vendors often shipped carefully optimized floating point libraries, which would result in floating-point optimized code from their compilers outperforming gcc, but for fixed point performance GCC was often competitive and even superlative to the offerings from RISC vendors. If you look through the history of SPEC benchmarks, you'll see that for SPECint, GCC was as much the compiler of choice for RISC vendors as it was for CISC vendors.
- housel 12y agoIn 1990-1991, in my first job, I insisted on using gcc on SunOS primarily because I wanted to use ANSI C89 features (primarily function prototypes). These were already available on the other two platforms we were targeting (the Microsoft C compiler, and Apple Macintosh Programmers Workbench), and the standard SunOS PCC-based compiler didn't support any of the new Standard C features.
- bane 12y agoIn college, I was excited about GCC because it was free as in beer, worked well, and the other compilers we could use were hundreds or thousands of dollars.