I just tried to build ioquake3 with:
> clang -v
clang version 2.8 (trunk)
Target: x86_64-portbld-freebsd8.1
Thread model: posix
And unlike the last time I tried everything works out of the box.
Even the tools/ are now built successfully.
Clang emits some code style warnings, I think they might at least
be worth looking at.
E.g. is there a good reason to enclose <code> in an "if (<code>);"?
There is no performance difference. I assume my performance is
limited by my crappy onboard video card, but building with clang
is considerably faster:
> time -h gmake -j3 CC=gcc
...
1m14.20s real 2m12.60s user 8.19s sys
> time -h gmake -j3 CC=clang
...
43.60s real 1m11.31s user 9.26s sys
That's only 59% of gcc's build time on my notebook.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
_______________________________________________
ioquake3 mailing list
[email protected]
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.
