Slashdot stories can be listened to in audio form via an RSS feed, as read by our own robotic overlord.

 



Forgot your password?
typodupeerror
Programming Operating Systems IT Technology BSD

GCC Compiler Finally Supplanted by PCC? 546

Posted by ScuttleMonkey
from the all-good-things-must-end dept.
Sunnz writes "The leaner, lighter, faster, and most importantly, BSD Licensed, Compiler PCC has been imported into OpenBSD's CVS and NetBSD's pkgsrc. The compiler is based on the original Portable C Compiler by S. C. Johnson, written in the late 70's. Even though much of the compiler has been rewritten, some of the basics still remain. It is currently not bug-free, but it compiles on x86 platform, and work is being done on it to take on GCC's job."
This discussion has been archived. No new comments can be posted.

GCC Compiler Finally Supplanted by PCC?

Comments Filter:
  • by gambolt (1146363) on Monday September 17, 2007 @11:09AM (#20637621)
    OK, so it compiles C on x86. What do I use when I want to compile objective C on my microwave?
  • Quick! (Score:5, Funny)

    by perbu (624267) on Monday September 17, 2007 @11:10AM (#20637639)
    Someone relicense it under the GPL!
  • *yawn* (Score:5, Funny)

    by blackcoot (124938) on Monday September 17, 2007 @11:13AM (#20637687)
    call me when pcc does something useful, like, say, working.
  • by sinnergy (4787) on Monday September 17, 2007 @11:16AM (#20637733) Homepage
    Your argument holds no water. If that were the case, one could make the same arguments about operating systems. Why bother developing Linux in an attempt to "keep up with the Jones'" when Windows already exists.

    I'm just sayin'...
  • by mrchaotica (681592) * on Monday September 17, 2007 @11:35AM (#20638107)

    You just restated point #2.

  • by Garridan (597129) on Monday September 17, 2007 @11:45AM (#20638279)
    Please. I think RMS would prefer, GNU/NetBSD != GNU/Linux. Obey the beard!
  • by Anonymous Coward on Monday September 17, 2007 @11:58AM (#20638547)
    And he continues to write code in C...why?
  • by nuzak (959558) on Monday September 17, 2007 @12:04PM (#20638687) Journal
    > It's like that phony debate between "great taste" and "more filling"

    That's "tastes great" and "LESS filling". Clearly you're trying to push a "tastes great" agenda by deliberately misrepresenting the opposing viewpoint. Typical tactics for the tasteistas.

    (imagine Daffy Duck saying all that)
  • GCC (Score:3, Funny)

    by MrCopilot (871878) on Monday September 17, 2007 @04:13PM (#20643063) Homepage Journal
    So is there an Arm-Linux-Pcc? CrossCompiler? Will I have to change my code?

    Then the answer is no. I may be alone in the world but I'm perfectly happy with the gcc compiler and have been for years. It does what its supposed to, It is FREE, It is crossplatform (MingW), and it annoys the BSD guys.

    Clear Winner. GCC

    It has been pointed out here, that people who choose a compiler based on its license are idiots. Well if I'm working on windows I use MingW specifically because of its license. If I'm working in Linux and I usually am, I choose GPL above all others. Count me as an Idiot if you like, But you can shove the alternatives. I know what I am getting and have a reasonable expectation what is coming in the future, and if I need to modify it (Heaven Forbid) I can. BSD is a fine license for people who NEED it. I don't. When given the choice I choose GPL. GCC Slower, maybe so. Code works and I get paid. If it takes 3 hrs for QT to compile. I bill for 3Hrs.

    Sorry but, I'm a pragmatist in all things except freedom. I've been burned enough. (Admittedly, I've personally never been burned by BSD code, unless you count Windows.)

  • Think about it. Getting a new compiler into free UNIX and the open source community is going to be as hard as getting a new platform on the desktop to compete with Windows. And for similar reasons.

    You're not going to supplant GCC until you get all the code that depends on GCC-specific features modified to be standard portable C. That's a barrier to entry as steep as Microsoft's application barrier to entry. Now it's not as bad as it was in the early '90s when GCC was sprouting new C extensions everywhere (like the ability to have declarations not at the start of blocks, or the ability to leave the second element out of the trinary conditional operator, or things like alloca), and a lot of those features have now become common and even standardized (and others, like the shortcut trinary, have been deprecated). But it's not as easy as just having a good compiler, or even a good language translating ecosystem like Tendra... the playing field is anything but level.
  • by Hal_Porter (817932) on Tuesday September 18, 2007 @02:48AM (#20648693)
    And he continues to write code in C...why?

    Because maintaining a secure system written in C requires paranoia, obsessive concentration on small details and merciless flaming of n00bs when they screw up.

An inclined plane is a slope up. -- Willard Espy, "An Almanac of Words at Play"

Working...