On 6/4/06, Carlo Marcelo Arenas Belon wrote:
PS. eventhough it wasn't the cleanest build, gcc-4.1.1 when used to build
everything but op.c resulted in working binaries on my gentoo 2006.0 amd64
system.
did you get better benchmark results than using gcc-3.x ?
--
Christian
Greetings,
attached patch, adds a ./configure option for setting the C compiler that will
be used to build op.c for each of the targets; letting the user compile
everything else with gcc 4.x if configured as the default C compiler while
isolating the opcode generation which currently relies in
On Sunday 04 June 2006 09:59, Carlo Marcelo Arenas Belon wrote:
Greetings,
attached patch, adds a ./configure option for setting the C compiler that
will be used to build op.c for each of the targets; letting the user
compile everything else with gcc 4.x if configured as the default C
SNIP
Why bother? As you say gcc4 has issues other than just op.c, so why not just
compile everything with the old gcc?
using the new gcc for the parts that can compile with it, could lead to better
performance in some cases, as well to help clean up the code for conformance
to newer standards
