public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* Result of 20070421 snapshot on ppc64
@ 2007-04-23 11:19 Srinivasa Ds
  2007-04-23 16:11 ` Martin Hunt
  0 siblings, 1 reply; 2+ messages in thread
From: Srinivasa Ds @ 2007-04-23 11:19 UTC (permalink / raw)
  To: systemtap

Since we are encountering some problem in systemtap.syscall tests. I
have modified the script "testsuite/systemtap.syscall/syscall.exp".

I have added "set flags "additional_flags=-m64"" for 64-bit compilation.
 Now I have 3 less errors.  Iam not sure,if this is the right way or not.
=========================
if {$srcdir == ""} {
        set pattern "*.c"
    } else {
        set pattern "$srcdir/$subdir/*.c"
    }
        set flags "additional_flags=-m64"  ===> added this stmt.
    foreach filename [lsort [glob $pattern]] {
        set file [file tail [string range $filename 0 end-2]]
        if {![installtest_p]} { untested $file; continue }
        target_compile $filename $wd/$file executable $flags
        send_log "Testing ${file}\n"
        set res [exec $srcdir/$subdir/test.tcl $file $filename]
        if {$res == "PASS"} {
==================================
===============================================================
Date: 200704230439
User: root
Kernel: Linux 2.6.21-rc7 #5 SMP Mon Apr 23 09:48:27 IST 2007 ppc64 ppc64
ppc64 GNU/Linux

Testsuite summary of failed tests
FAIL: probefunc:kernel.function("context_switch").inline compilation
(PR 2436)
FAIL: buildok/lket.stp (PR 3833)
FAIL: buildok/process_test.stp
FAIL: buildok/socket.stp
FAIL: systemtap.samples/lket(semantic error)
FAIL: sysopen (1)   (PR 3429)
FAIL: mmap          (PR 4088)
FAIL: readwrite
FAIL: signal
FAIL: statfs
FAIL: 32-bit alarm   (PR 4332)
FAIL: 32-bit clock    (PR 4332)
FAIL: 32-bit mmap     (PR 4088)
FAIL: 32-bit readwrite
FAIL: 32-bit signal   (PR 4332)
FAIL: 32-bit stat     (PR 4332)
FAIL: 32-bit statfs   (PR 4332)
                === systemtap Summary ===

# of expected passes            332
# of unexpected failures        17
# of expected failures          129
# of known failures             4
# of untested testcases         7
# of unsupported tests          2
runtest completed at Mon Apr 23 12:16:54 2007
========================================================

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Result of 20070421 snapshot on ppc64
  2007-04-23 11:19 Result of 20070421 snapshot on ppc64 Srinivasa Ds
@ 2007-04-23 16:11 ` Martin Hunt
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Hunt @ 2007-04-23 16:11 UTC (permalink / raw)
  To: Srinivasa Ds; +Cc: systemtap

On Mon, 2007-04-23 at 16:46 +0530, Srinivasa Ds wrote:
> Since we are encountering some problem in systemtap.syscall tests. I
> have modified the script "testsuite/systemtap.syscall/syscall.exp".
> 
> I have added "set flags "additional_flags=-m64"" for 64-bit compilation.
>  Now I have 3 less errors.  Iam not sure,if this is the right way or not.

If I understand this correctly, the default on ppc64 is to build 32-bit
binaries, so 64-bit needs forced. This seems like a general problem on
64-bit systems where syscall.exp should not make assumptions and should
run two passes; one with -m64 and one with -m32.

Your modification is correct for ppc64, but would break other systems.
I'll modify it some more and check it in.

Martin


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-04-23 16:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-04-23 11:19 Result of 20070421 snapshot on ppc64 Srinivasa Ds
2007-04-23 16:11 ` Martin Hunt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).