From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24219 invoked by alias); 26 Jun 2004 23:28:45 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 24212 invoked from network); 26 Jun 2004 23:28:44 -0000 Received: from unknown (HELO mclean.mail.mindspring.net) (207.69.200.57) by sourceware.org with SMTP; 26 Jun 2004 23:28:44 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by mclean.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BeMbD-0000XB-00; Sat, 26 Jun 2004 19:28:43 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 1D36F4B104; Sat, 26 Jun 2004 19:28:48 -0400 (EDT) To: gdb@sources.redhat.com, tausq@debian.org Subject: native hppa2.0w-hp-hpux11.00, 32-bit versus 64-bit Message-Id: <20040626232848.1D36F4B104@berman.michael-chastain.com> Date: Sat, 26 Jun 2004 23:28:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-06/txt/msg00259.txt.bz2 We've got this test script to print hp register values, gdb/testsuite/gdb.hp/gdb.base-hp/reg.exp. I'm working on it because the hp register code changed between 6.1 and HEAD. There's some cosmetic differences in the results, which are easy for me to fix, and there's some 32-bit/64-bit changes, which I need help with. I'm testing with gdb 6.1.1 and with gdb HEAD 2004-06-01. My gdb's are native hppa2.0w-hp-hpux11.00, and I built them with gcc 3.3.2 using no special flags. Here is my actual output: # gdb 6.1.1 # gdb built with gcc 3.3.2, no special flags (gdb) info reg r19 r19 deadbeefbadcadee (gdb) print /x $r19 $1 = 0xbadcadee^M # gdb HEAD 2004-06-01 # gdb built with gcc 3.3.2, no special flags (gdb) info reg r19 r19 0xbadcadee 3135024622 (gdb) print /x $r19 $1 = 0xbadcadee^M The inferior program has used assembly language to build a 64-bit value in $r19, and I'm using gdb to examine the value. In three of these four instances, there's 32-bit truncation going on. I need to figure out how to mark these in the test suite. In my view, the only correct result is the full 64-bit result. I want to make the test results be: # gdb 6.1.1 PASS: gdb.base-hp/reg.exp: info reg r19 KFAIL: gdb.base-hp/reg.exp: print /x $r19 (pr gdb/NNNN) # gdb HEAD 2004-06-01 KFAIL: gdb.base-hp/reg.exp: info reg r19 (pr gdb/NNNN) KFAIL: gdb.base-hp/reg.exp: print /x $r19 (pr gdb/NNNN) The alternative would be to consider 32-bit truncation to be okay issue a PASS on all four results. Advice please? Michael C