[Bug tapsets/11708] New: SDT on i686 is register-poor

[jistone at redhat dot com]

Seen while running the testsuite/systemtap.base/sdt.exp:

Host: Linux vm-f13-32 2.6.33.5-112.fc13.i686 #1 SMP Thu May 27 03:11:56 UTC 2010
i686 i686 i386 GNU/Linux
Snapshot: version 1.2/0.147 commit release-1.2-277-gd1274b5
GCC: 4.4.4 [gcc (GCC) 4.4.4 20100503 (Red Hat 4.4.4-2)]
Distro: Fedora release 13 (Goddard)
[...]
Running /home/jistone/systemtap/testsuite/systemtap.base/sdt.exp ...
[...]
Executing on host: gcc /home/jistone/systemtap/testsuite/systemtap.base/sdt.c 
-g -I/home/jistone/systemtap/testsuite/../includes -Wall -Wextra -Werror -O2 
-lm   -o sdt.c.exe.5    (timeout = 300)
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c: In function ‘main’:
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: can't find a
register in class ‘GENERAL_REGS’ while reloading ‘asm’
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:35: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:40: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:45: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: ‘asm’ operand
has impossible constraints
compiler exited with status 1
output is:
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c: In function ‘main’:
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: can't find a
register in class ‘GENERAL_REGS’ while reloading ‘asm’
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:35: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:40: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:45: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: ‘asm’ operand
has impossible constraints

FAIL: compiling sdt.c additional_flags=-O2 uprobe
UNTESTED: sdt additional_flags=-O2 uprobe
Executing on host: gcc /home/jistone/systemtap/testsuite/systemtap.base/sdt.c 
-g -I/home/jistone/systemtap/testsuite/../includes -Wall -Wextra -Werror "-O3" 
-lm   -o sdt.c.exe.6    (timeout = 300)
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c: In function ‘main’:
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: can't find a
register in class ‘GENERAL_REGS’ while reloading ‘asm’
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:35: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:40: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:45: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: ‘asm’ operand
has impossible constraints
compiler exited with status 1
output is:
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c: In function ‘main’:
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: can't find a
register in class ‘GENERAL_REGS’ while reloading ‘asm’
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:35: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:40: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:45: error: ‘asm’ operand
has impossible constraints
/home/jistone/systemtap/testsuite/systemtap.base/sdt.c:50: error: ‘asm’ operand
has impossible constraints

FAIL: compiling sdt.c additional_flags="-O3" uprobe
UNTESTED: sdt additional_flags="-O3" uprobe

-- 
           Summary: SDT on i686 is register-poor
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: jistone at redhat dot com


http://sourceware.org/bugzilla/show_bug.cgi?id=11708

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.