> then it's broken by design ... sure the idea about how qemu goes about its
> emulation is pretty goddamn cool, but gcc has never said that you can rely on
> certain behavior
very right!
but you cannot change the world :-(
signature.asc
Description: OpenPGP digital signature
> I've been thinking about this recently. What qemu does is compile a C
> implementation of the target processor's instruction set into an object
> file when qemu is built, then at run-time (JIT time) it cut-n-pastes
> bits of that object file when it "compiles" the target executable into
> native
Sven Köhler wrote:
some software, like qemu and others, are simply not compatible with gcc
4.x and they will not become compatible due to severe conceptional issues.
then they stay broken ... add a warning to the ebuild if `gcc-major-version`
is "4" (see toolchain-funcs.eclass)
Hmm
>> some software, like qemu and others, are simply not compatible with gcc
>> 4.x and they will not become compatible due to severe conceptional issues.
>
> then they stay broken ... add a warning to the ebuild if `gcc-major-version`
> is "4" (see toolchain-funcs.eclass)
Hmm, but ...
there is t
