At 4:12 Uhr +0100 05.02.1998, Gordon W. Ross wrote:

>Yes, all self-modifying code should definitely flush the I-cache.

[...]

>Hmmm... Looks like that _cachectl code should be copied into
>libgcc2.a (well, into libc in our case):
>
>It would be nice if we could let a simple "trap #2" do the job of
>flushing the I-cache as needed for self-modifying code to work.
>That's what "trap #2" does on SunOS (their dynamic linker uses it).
>Also it was implemented as a "fast trap" (no "rei" check, just rte)
>so we could do the same and let both our executables and SunOS
>enjoy the availability of a very cheap I-cache flush.
>
>BTW, we no longer use "trap #2" for kernel breakpoints, so we
>could now easily let it mean "flush the I-cache".  Good idea?

Sounds good to my untrained ears.  ;)

"It would be nice...." -- Would it be of any help if I send-pr'ed? Or could
you?

	hauke



--
"It's never straight up and down"     (DEVO)