[Info-vax] Some questions on software for VMS 7.3 VAX

[hb]

On 01/26/2016 08:02 AM, lists at openmailbox.org wrote:
> I thought you said you got it to crash by control-X space. If so this isn't
> limited to dired. Maybe the whole thing needs to be compiled /noopt and
> then it will probably be unusable. The other option if you really want to
> compile it like it was "designed" to be compiled if there indeed is any
> such thing would be to get the comtemporaneous port of gcc for VAX/VMS and
> build with that. gnu crapware is not guaranteed to build or work with
> anything but gcc and bash and then only sometimes.

With ^X^F and space, which for me seems to be more or less the same
thing as meta-x and dired. I had alread everything compiled with /noopt
(and /debug - which may have contributed to the oversight of this
problem, as I made the "binary kit" with /opt and do not have or know of
test procedures). Depending on the VAX emulation and/or hardware the
performance may be acceptable. But you already said, it is slow.

>> > Anybody wants to try the workaround, anyway?
> Sure if you want to spend the time messing around with it I'll gladly test
> it and get back to you. Especially the gcc idea sounds promising because
> the optimizations seem essential and that is less likely to break badly.

I'm not sure I want to go the gcc route. I don't know whether there is a
contemporary version of gcc for VAX/VMS. This is old stuff and it is fun
to play with it, but that's all. I will try to find out, what the cause
of the problem is. The good thing is, it is not in Emacs' memory
management, which is code, which I prefer not to touch. Sooner or later
I will make my source code changes available so someone can try gcc on them.