|Compiler-generated file access hints email@example.com (Nor Jaidi) (1997-04-02)|
|Re: Compiler-generated file access hints firstname.lastname@example.org (Stefan Monnier) (1997-04-03)|
|Re: Compiler-generated file access hints email@example.com (Nor Jaidi) (1997-04-06)|
|From:||Nor Jaidi <firstname.lastname@example.org>|
|Date:||6 Apr 1997 22:26:42 -0400|
|Organization:||Curtin University of Technology|
Stefan Monnier wrote:
> No special string or file knowledge wouldn't be necessary any more in
> the compiler. Of course, then you'll also have to make sure this
> skeleton program is run "a little in advance".
I like your idea and will put it in my list of things to squeeze my
brain with. But it is still a forest to me. Running "a little in
advance" means (as I understand it) interlacing the skeleton code with
the "normal" code and making sure that the prefetch version of file
access are placed as far back as possible from the normal version to
allow the prefetch to complete. We have to scan the source backward,
scan for dependencies backward (possibly into function calls that
might change vars that store filename, seek position, etc) and
backpatch the object tree. Hei, someone please tell me: do you see
any neat way to do this? Multi-pass? That's not neat.
Nor Jaidi Tuah
Return to the
Search the comp.compilers archives again.