ppc64 - unresolved target-symbols $fd

[Hien Nguyen]

It appears that the problem is fixed with the kernel-debuginfo compiled 
with ggc v3.4.6 20060404 that came with RHEL4-U4 beta.

However, the following error re-surfaces
#stap -up4 -vv sys.stp
[....]
 gcc -m64 -Wp,-MD,/tmp/stapsWNb3r/.stap_25372.o.d -nostdinc -iwithprefix 
include -D__KERNEL__ -Iinclude  -Wall -Wstrict-prototypes -Wno-trigraphs 
-fno-strict-aliasing -fno-common -Os -g -Wdeclaration-after-statement 
-msoft-float -pipe -mminimal-toc -mtraceback=none 
-mcall-aixdesc                   -mtune=power4 -fno-unit-at-a-time 
-freorder-blocks -Wno-unused -Werror 
-I"/root/stap_testing_200606121452/src/runtime"   -DMODULE 
-DKBUILD_BASENAME=stap_25372 -DKBUILD_MODNAME=stap_25372 -c -o 
/tmp/stapsWNb3r/.tmp_stap_25372.o /tmp/stapsWNb3r/stap_25372.c
{standard input}: Assembler messages:
{standard input}:639293: Error: operand out of range (0x0000000000008000 
is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:639386: Error: operand out of range (0x0000000000008008 
is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:639547: Error: operand out of range (0x0000000000008010 
is not between 0xffffffffffff8000 and 0x0000000000007fff)
{standard input}:639558: Error: operand out of range (0x0000000000008018 
is not between 0xffffffffffff8000 and 0x0000000000007fff)
[....]

I thought the issue above was fixed with '-mminimal-toc'.
Hien.

Hien Nguyen wrote:
> This issue might be duplicated in #2438
>
> stap -up4 -vv -e'probe syscall.fstat{}'
> ....
> semantic error: unresolved target-symbol expression: identifier '$fd' 
> at /root/stap_testing_200606121452/src/tapset/syscalls.stp:697:12
> semantic error: unresolved target-symbol expression: identifier '$fd' 
> at /root/stap_testing_200606121452/src/tapset/syscalls.stp:699:31
> ....