#optimizer fix
12-Apr-95 18:09:38
Sb: #46497-#optimizer fix
Fm: Greg Comeau@Comeau Cmptg 72331,3421
To: James Du Bois 72237,32
> Sorry, but it IS compiling a jump to 0x4, I watched it jump to 0x4
>using the debugger. I think it is an indirect JSR call, but since I know
>almost no assembler, the assem. source means almost nothing to me.
I don't know what the I&D situation is on the Amiga
(it's been years since I toyed with that kinda stuff and
forget which chips and OSs do what), but there is a big difference
in your executing (seeing) a jmp to 4 in your debugger or the compiler
generating the jump or the RTL routine doing it or etc.
These may seem like pedantic differences, but they all present
totally different scenarios. Finding out which is your case is
the issue. For instance, perhaps what you're seeing executed is
some data somewhere that the program "inadvertantly" got to via
some uninitialized function pointer or somesuch. I have a cliche
I use often when I lecture on C and C++, more applicable to source
but, but it is probably applicable here to:
What you see is what you get. — Anonymous
What you see is all you get. — Brian Kernighan
What you see is what you see. What you get is what you get. — Greg Comeau
This (unfortunately?!) encompasses many things, programming and otherwise
and is "what the fun is about." 😉