|
General software and network General OS-independent software and network questions, X11, MTA, routing, etc. |
|
Thread Tools | Display Modes |
|
|||
The PCC project seeks donations for ambitious 1.0 release.
So, Yesterday it seems Anders Magnusson put out a call for donations..
http://undeadly.org/cgi?action=artic...20081108135831 PCC is already at an awesome stage, several developers have revived old targets... and it can already compile both OpenBSD's and NetBSD's userland and kernel. If you have a few dimes to spare, perhaps you can help them work on the few remaining issues. http://www.bsdfund.org/projects/pcc/ |
|
|||
Quote:
Adam |
|
|||
Woah, Did either of you read what I wrote? It's PCC(Portable C Compiler), not PPC.
|
|
|||
I think its awesome that they what to develop the entire toolchain to be able to (hopefully) boot GNU from the base BSD.
I read some responses on Digg (I think) that was saying that PCC wasn't very capable of creating optimized code like GCC. Does anyone know anything of this? Has the PCC team come out with any sort of benchmark comparisons?
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
||||
Quote:
The advantages of PCC are numerous. It is only C compiler unlike GNU Frankenstein. It is extremely portable. I think that it took only 2 days to port it to i386. It is clean and simple. Originally PCC was written in late seventies by Stephen C. Johnson who was a professional mathematician and the member of legendary Bell Labs as a main C compiler for ATT Unix on PDP 11(Legendary DEC machine). It is much faster than GCC. It takes about one third of time for PCC to compile the same code as GCC. You will be actually able to compile Firefox in half an hour. As BSD666Fan already mentioned that PCC is only 5MB of code while GCC is about 250MB. I can not wait for my default OpenBSD installation to slim down from 550MB to less than 300MB. If the developers of Dillo2 make serious progress (add OpenSSL support and possibly idiotic Java Script Engine) the only monster that I would have to keep would be TeX. I really wish Donald Knuth have cleaned up Troff instead of cooding Damn Small Linux here is coming damn small OpenBSD:-) Lately GCC started dropping support for non-Wintel architectures which did upset many old Unix guys who still want to run their Alphas, Vaxes, and other more exotic ROCK stable hardware. This is the greatest news possibly since the release of 4.4 BSD lighte. Last edited by Oko; 9th November 2008 at 12:57 AM. |
|
||||
Quote:
Quote:
Quote:
Quote:
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
|||
Quote:
What would it be required? C++ is not used in the kernel or userland.. as a system compiler it would most definitely be a candidate for replacing the local gcc compiler. In the future, perhaps pcc (and a binutils replacement..) will be part of comp??.tgz and GCC/binutils will only available as ports. |
|
|||
Quote:
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
||||
Quote:
C and C++ are related languages, but they are different languages. If the same compiler did both, C++ would probably boat it like a truck horse at an all you can eat anyway. Footnote: Whatever the opinions of some people as to it's meaning, to me the phrase "C/C++" only means "C and C++"
__________________
My Journal Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''. |
|
||||
Thread split to The big TeX and (g)troff thread, please continue all Tex/(g)troff discussion there.
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
|
|||
Quote:
And, if I read their website correctly, it compiles f77 code, which is much different from C than C++.
__________________
And the WORD was made flesh, and dwelt among us. (John 1:14) |
|
|||
Quote:
I'm still not understanding your desire for C++, it's an entirely different language... Now, perhaps it's a lack of understanding.. but you do not need a C++ compiler to build either gcc or g++, GNU's C++ compiler is written in C. |
|
||||
Quote:
|
|
|||
Quote:
Now, GCC stands for "GNU Compiler Collection", PCC stands for "Portable C Compiler". GCC is a collection of compilers for different languages, PCC is a C compiler... a BSD licenced C compiler. Presumably, 3rd party ports could be compiled by GCC if necessary, or PCC if they're not an absolute compatibility nightmare. |
|
|||
As far as I understand newer versions of Gcc have dropped support for some architectures/hardware platforms. That is the reason, why for example NetBSD is forced to use older Gcc versions for some CPUs, while they only can use the newest Gcc for the i386 and amd65 platforms.
Wile gcc has the name of being an open source project, it is actually run by a few companies, which, if they don't see any need to still support an older CPU, just drop support. Fromhttp://gcc.gnu.org/gcc-4.0/changes.html Quote:
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
Quote:
Port X needs C++ compiler, install g++ as dependency. Code:
Tools/packages necessary for building GCC ISO C90 compiler Necessary to bootstrap GCC, although versions of GCC prior to 3.4 also allow bootstrapping with a traditional (K&R) C compiler. To build all languages in a cross-compiler or other configuration where 3-stage bootstrap is not performed, you need to start with an existing GCC binary (version 2.95 or later) because source code for language frontends other than C might use GCC extensions. ... Sounds simple enough, not fun, but simple enough lol. realistically I would expect to see gcc, g++, and pcc all in the base systems compiler dist set for awhile; the question is which one will be /usr/bin/cc and friends? At the point where the OS can be compiled with pcc and pcc can handle getting GCC up for ports/pkgsrc - do they really need gcc in the base after that?
__________________
My Journal Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''. |
|
||||
Dealing with c++ ports is easy, just add to the port Makefile:
Code:
BUILD_DEPENDS= lang/gcc42
__________________
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Need suggestions on what to name this project | TerryP | Off-Topic | 10 | 6th November 2010 03:13 PM |
C project to study | maxrussell | Programming | 10 | 23rd January 2009 08:47 AM |
Project layout, any comments? | PatrickBaer | FreeBSD General | 1 | 12th October 2008 05:13 PM |
Suggestions for my honours degree project... | scotsman | FreeBSD General | 7 | 20th September 2008 01:38 PM |
FreeBSD 6.2-RELEASE > 7.0-RELEASE Upgrade | Marci | FreeBSD Installation and Upgrading | 2 | 23rd July 2008 02:10 PM |