Re: [Sablevm-developer] Instruction cache flush (non)portability

[Grzegorz P. <ga...@de...>]

W li=B6cie z wto, 19-11-2002, godz. 18:23, Grzegorz Prokopski pisze:=20
> Hi!
I was a bit in a hurry, so see the corections below.

(below paragraph is about already compiled binary version
of sablevm which should survive upgrade of glibc, gcc etc.)
> It's even more complicated if we link to that symbol and it's
> definition changes. On i386 (and most of the arches) we're
> _staticly_ linked to libgcc2 library (which contains the symbol).
> Thus - we don't have to worry about gcc upgrades etc.
> However on some arches, like m68k
this lib (libgcc2) is dynamically linked with every program
> - or so I was told
=20
> I personally would vote that we use this symbol in one of next
> versions, after my old "every arch" patch is applied.
Not sure yet, but it would be possible to use
#include <linux/types.h>
when available and fallback to autodetection when it fails.

BTW: I was yet unable to actually test that __clear_cache
function (sorry), because it does nothing for i386 and Bdale
is very busy today so we haven't managed to test that for ia64
yet :-/

(I have assembler version for ia64 ready for another test anyway)

					GBP