John O Goyo <address@hidden> writes:
Gaius
The code is indeed in the assembler file.
SymbolTable_GetVarPointerCheck
.PROC
.CALLINFO FRAME=128,CALLS,SAVE_RP,SAVE_SP,ENTRY_GR=3
.ENTRY
stw %r2,-20(%r30)
copy %r3,%r1
copy %r30,%r3
stwm %r1,128(%r30)
stw %r3,-4(%r30)
stw %r26,-36(%r3)
ldw -36(%r3),%r26
.CALL ARGW0=GR
[...]
However, the code did not seem to make it into the object file.
heap% nm FIO.o |grep FIO_OpenToRead
FIO_OpenToRead | 0|extern|entry |$CODE$
I do not understand this -- I clearly need to understand the build
process better.
really odd, I suspect you need to follow the build process when
GM2_FLAGS includes the -v option. This will show which assembler is
used and maybe then a tiny program can be substituted instead of
SymbolTable.mod, the .s file examined and the .o file as well.
Finally I find it useful to recreate a similar tiny source file in C
and then run ./xgcc -v -c foo.c (when in build-4.1.x/gcc) as a
reference.