Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

GCC -The speed king

Name: Anonymous 2009-07-02 12:32

There are no compilers that will ever approach the speed of gcc,
Especially your toy languages.

Name: Anonymous 2009-07-02 12:44

GHC begs to differ boy.

Name: FrozenVoid 2009-07-02 12:55

>>1 FASM generated code can be much faster.
Plus you get to abuse the full hardware potential.
P.S. People who talk about portability, forget mountains of non-portable 32-bit x86 code drive the entire software industry and will do so for at least 10-15 years.

_____________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
The knowable world is incomplete if seen from any one point of view, incoherent if seen from all points of view at once, and empty if seen from nowhere in particular

Name: FrozenVoid 2009-07-02 12:58

>>3 Also, most of it is closed-source.
____________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
Flags are bits of colored cloth that governments use first to shrink-wrap people's brains and then as ceremonial shrouds to bury the dead.

Name: Anonymous 2009-07-02 13:13

Citation Needed

Name: Anonymous 2009-07-02 13:17

>>3
forget mountains of non-portable 32-bit x86 code drive the entire software industry and will do so for at least 10-15 years.
Did you perhaps omit a ``that'' in that expression (between ``code'' and ``drive'')? It would make more sense that way.

Name: Anonymous 2009-07-02 13:23

>>5
 http://dis.4chan.org/read/prog/1246552333/3,4 ISBN-101324000930024248
 Frozen Void (2009) "Software portability on the PC", Prog Enterprise Publications
"...mountains of non-portable 32-bit x86 code drive the entire software industry"(2009)

Name: Anonymous 2009-07-02 13:26

The Stalin Scheme Compiler begs to differ

Name: Anonymous 2009-07-02 13:43

>>7
Reference cycle detected... pruning

Name: Anonymous 2009-07-02 13:48

>>1
GCC is a horrendous piece of shit. The only reason to even consider keeping it around is if you're stuck writing Sepples.

Have you ever tried to work on the backend? Go do so, and kill yourself out of frustration.

Name: Anonymous 2009-07-02 13:51

I will never again ever in my life ever compile straight C with GCC ever again ever. Gay C is fine though. That's why it's the Gay C Compiler.

Name: Anonymous 2009-07-02 15:16

>>7
There appears to have been a transcription error. I cannot utilize the ISBN while the check digit is inconsistent. Please advise immediately.

Name: Anonymous 2009-07-02 15:36

I wonder, how would you use LLVM to compile C?

Name: Anonymous 2009-07-02 17:08

>>13
LLVM is a toy compiler. You can't write anything useful with it.

Name: Anonymous 2009-07-02 17:54

GCC is a good C compiler but nothing can beat MSVC when it comes to C++.

Name: Anonymous 2009-07-02 18:01

>>1
You're trolling but I don't want anyone to get the wrong impression: GCC is amongst the worst compilers. MSVC and ICC trash it both in compilation speed and in speed of the generated code.

>>2
GHC is just a GCC frontend that generates C code, so you'll always be able to at least match it win C code compiled with GCC.

Name: Anonymous 2009-07-02 19:03

>>16
GHC is not a GCC front end, it is a separate compiler from the ground up. While I don't know hte performance of GHC off the top of my head, I don't want people to get the idea that GHC is limited by GCC's optimization abilities.

Name: Anonymous 2009-07-02 19:07

>>16
GHC gives you the option of generating (pre-optimized) C code. That's not the same as being a GCC front-end. 0/10 kill yourself

Name: Anonymous 2009-07-02 19:11

GCC is an ugly mess of a compiler. It's optimizations are bottom of the barrel (though they are slowly improving) and hte code base is completely and utterly disastrous. You will want to kill yourself the moment you deal with it.

LLVM is the future, sadly it's still using GCC as a front end, however I think it will be a much more useful platform for compiler development once it's matured a bit more. Also once it's C/C++ front end(clang) is out.

Name: Anonymous 2009-07-02 19:12

>>19
clang is "out" but it sucks right now. I'm pregnant

Name: Anonymous 2009-07-02 19:16

>>20
Oh right. To clarify  I meant "out" as in "able to compile any C++ code that's worth a damn".

Name: Anonymous 2009-07-02 20:27

>>20
clang clang clang

Name: Anonymous 2009-07-02 20:47

cfront ne1

Name: Anonymous 2009-07-02 21:26

>>21
Fuck no, you're not using clang for Sepples for at least a couple more years. That's what LLVM-GCC is for.

It works with C just fine though.

Name: FrozenVoid 2009-07-03 2:07

>>24 I'll try it today. Hope its not buggy.(I don't use C++)


________________________________________
http://xs135.xs.to/xs135/09042/av922.jpg
Those who dream by night in the dusty recesses of their minds wake in the day to find that it was vanity: but the dreamers of the day are dangerous men, for they may act their dreams with open eyes, to make it possible.

Name: FrozenVoid 2009-07-03 2:13

If you would like to check out and build Clang, the current procedure is as follows:

   1. Checkout and build LLVM from SVN head:
          * svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm
          * cd llvm
          * ./configure; make
   2. Checkout Clang:
          * From within the llvm directory (where you built llvm):
          * cd tools
          * svn co http://llvm.org/svn/llvm-project/cfe/trunk clang
   3. If you intend to work on Clang C++ support, you may need to tell it how to find your C++ standard library headers. If Clang cannot find your system libstdc++ headers, please follow these instructions:
          * 'touch empty.cpp; gcc -v empty.cpp -fsyntax-only' to get the path.
          * Look for the comment "FIXME: temporary hack: hard-coded paths" in clang/lib/Frontend/InitHeaderSearch.cpp and change the lines below to include that path.
   4. Build Clang:
          * cd clang (assuming that you are in llvm/tools)
          * make (this will give you a debug build)
   5. Try it out (assuming you add llvm/Debug/bin to your path):
          * clang-cc --help
          * clang-cc file.c -fsyntax-only (check for correctness)
          * clang-cc file.c -ast-dump (internal debug dump of ast)
          * clang-cc file.c -ast-view (set up graphviz and rebuild llvm first)
          * clang-cc file.c -emit-llvm (print out unoptimized llvm code)
          * clang-cc file.c -emit-llvm -o - | llvm-as | opt -std-compile-opts | llvm-dis (print out optimized llvm code)
          * clang-cc file.c -emit-llvm -o - | llvm-as | opt -std-compile-opts | llc > file.s (output native machine code)

      Note: Here clang-cc is the "low-level" frontend executable that is similar in purpose to cc1. Clang also has a high-level compiler driver that acts as a drop-in replacement for gcc.

Note that the C front-end uses LLVM, but does not depend on llvm-gcc. If you encounter problems with building Clang, make sure you have the latest SVN version of LLVM. LLVM contains support libraries for Clang that will be updated as well as development on Clang progresses.

Amazing they haven't got a download section yet.Well, i'll check them in 2-3 years.

_______________________________
http://xs135.xs.to/xs135/09042/av922.jpg
Experience comprises illusions lost, rather than wisdom gained.

Name: Anonymous 2009-07-03 4:39

>>26
Of course they have a download section.  You linked to it twice.

Name: Anonymous 2010-11-28 1:22

<

Name: Anonymous 2010-12-17 1:30

Xarn is a bad boyfriend

Name: Anonymous 2011-02-03 8:31

Name: Anonymous 2012-03-28 2:25

my farts burn my anus
it hurts
in a good way

Don't change these.
Name: Email:
Entire Thread Thread List