Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Clang integration?
reckless:
yep noticed fixed the link ;)
if you only need c/c++ or fortran support it can replace the standard mingw.
there are a few quirks to get codeblocks running with it for one gcc and g++ are prefixed with llvm- so need to tell it that. the same goes for gfortran.
sorry about the size ill see if i can hammer it down some but this is mostly a test build.
Jenna:
Did you enable optimization ?
Otherwise, you create a debug-build and that's mauch larger (and slower).
There is switch for the configure-script, I don't know exactly how it is named (not on my system), but I guess it was --enable-optimization.
Search for it with ./configure --help .
If you use makefiles directly, the switch is named ENABLE_OPTIMIZED=1 .
reckless:
aye was set as debug compiling a release version now :) should be up in some hours unless i run into problems.
joubertdj:
For those of you who don't know ... Clang has successfully compiled the Linux Kernel ... hmmm ...
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-October/011711.html ... whoop ...
ollydbg:
--- Quote from: joubertdj on November 11, 2010, 10:11:35 am ---For those of you who don't know ... Clang has successfully compiled the Linux Kernel ... hmmm ...
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2010-October/011711.html ... whoop ...
--- End quote ---
great compiler!!!
I have one glance on the source code of clang's lexer and parser. it was quite (too) complex. All the lexer/ parser was hand-written. and their hand-written lexer doesn't distinguish with any identifiers and keyword. instead, they use an identifier hash table, once the lexer get a general identifier, it will be looked up in the identifier table to see if it was a keyword or a macro definition or a new real identifier...
the code snippet of parsing a function declaration was more than 800 lines. :shock:
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version