Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: "Hans-Peter Nilsson" <hp@bitrange.com>
Subject: Re: [PATCH] sim: make sure to include strsignal prototype
Date: Sat, 24 Mar 2012 04:12:00 -0000	[thread overview]
Message-ID: <201203240012.05447.vapier@gentoo.org> (raw)
In-Reply-To: <alpine.BSF.2.00.1203230114540.31229@dair.pair.com>

[-- Attachment #1: Type: Text/Plain, Size: 3683 bytes --]

On Friday 23 March 2012 01:24:07 Hans-Peter Nilsson wrote:
> Another thing I noticed: could you please adjust the
> sim/testsuite/sim/cris/c/ tests too?  Lots of "program stopped
> with signal" there; your earlier fixes seems to have been just
> to the asm/ subdir.  I'm not putting it on you to assemble a
> cris-elf toolchain to verify it (not that it shouldn't be
> obvious :) just do the same transformation as in asm/.

the cris sim gets into an infinite loop for me.  from the log:

Executing on host: cris-elf-gcc ../../../../sim/testsuite/sim/cris/c/append1.c  -O2  -lm   -o append1.c.x    (timeout = 300)
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-closer.o): In function `_close_r':
.../newlib-1.20.0/newlib/libc/reent/closer.c:53: warning: _close is not implemented and will always fail
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-fstatr.o): In function `_fstat_r':
.../newlib-1.20.0/newlib/libc/reent/fstatr.c:62: warning: _fstat is not implemented and will always fail
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-isattyr.o): In function `_isatty_r':
.../newlib-1.20.0/newlib/libc/reent/isattyr.c:58: warning: _isatty is not implemented and will always fail
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-lseekr.o): In function `_lseek_r':
.../newlib-1.20.0/newlib/libc/reent/lseekr.c:58: warning: _lseek is not implemented and will always fail
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-openr.o): In function `_open_r':
.../newlib-1.20.0/newlib/libc/reent/openr.c:59: warning: _open is not implemented and will always fail
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-readr.o): In function `_read_r':
.../newlib-1.20.0/newlib/libc/reent/readr.c:58: warning: _read is not implemented and will always fail
/usr/lib/gcc/cris-elf/4.5.3/../../../../cris-elf/lib/libc.a(lib_a-writer.o): In function `_write_r':
.../newlib-1.20.0/newlib/libc/reent/writer.c:58: warning: _write is not implemented and will always fail

Simulating .../sim/testsuite/sim/cris/c/append1.c with 
.../sim/cris/run    append1.c.x 
spawn .../sim/testsuite/../cris/run append1.c.x
WARNING: program timed out.
FAIL: crisv10 append1.c (execution)

running it by hand:
$ ./sim/cris/run -t ./sim/testsuite/append1.c.x
...
0x00167e #56   _fwalk          jump [sp+]        - sr <- 0x1680, gr <- 0x3dfffdb0, pc <- 0x9ba, xbit <- 0x0, insn-prefixed-p <- 0x0
0x0009ba #167  _cleanup_r      jump [sp+]        - sr <- 0x9bc, gr <- 0x3dfffdb4, pc <- 0x6ce, xbit <- 0x0, insn-prefixed-p <- 0x0
0x0006ce #65   exit            move.d r0,r10     - gr <- 0x1, nbit <- 0x0, zbit <- 0x0, xbit <- 0x0, insn-prefixed-p <- 0x0
0x0006d0 #65   exit            jsr 0x0000000000003582 - sr <- 0x6d6, pc <- 0x3582, xbit <- 0x0, insn-prefixed-p <- 0x0
0x003582 #11   _exit           ba 0x0000000000003582 - xbit <- 0x0, insn-prefixed-p <- 0x0, pc <- 0x3582
0x003584 #11   _exit           nop               - xbit <- 0x0, insn-prefixed-p <- 0x0
0x003582 #11   _exit           ba 0x0000000000003582 - xbit <- 0x0, insn-prefixed-p <- 0x0, pc <- 0x3582
0x003584 #11   _exit           nop               - xbit <- 0x0, insn-prefixed-p <- 0x0
0x003582 #11   _exit           ba 0x0000000000003582 - xbit <- 0x0, insn-prefixed-p <- 0x0, pc <- 0x3582
0x003584 #11   _exit           nop               - xbit <- 0x0, insn-prefixed-p <- 0x0
0x003582 #11   _exit           ba 0x0000000000003582 - xbit <- 0x0, insn-prefixed-p <- 0x0, pc <- 0x3582
0x003584 #11   _exit           nop               - xbit <- 0x0, insn-prefixed-p <- 0x0
... loops here forever ...
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-03-24  4:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  4:23 Mike Frysinger
2012-03-23  4:35 ` Mike Frysinger
2012-03-23  5:24 ` Hans-Peter Nilsson
2012-03-23 15:43   ` Mike Frysinger
2012-03-23 22:12     ` Hans-Peter Nilsson
2012-03-23 22:43       ` Mike Frysinger
2012-03-24  5:34     ` Mike Frysinger
2012-03-24  4:12   ` Mike Frysinger [this message]
2012-03-24  5:53     ` Hans-Peter Nilsson
2012-03-24  6:12       ` Mike Frysinger
2012-03-24  6:49         ` Hans-Peter Nilsson
2012-03-24 18:18           ` Mike Frysinger
2012-03-24 10:55   ` Finalizing fix committed for "[PATCH] sim: make sure to include strsignal prototype" Hans-Peter Nilsson
2012-03-24 18:24     ` Mike Frysinger
2012-03-24 20:55       ` Hans-Peter Nilsson
2012-03-25  8:14         ` Mike Frysinger
2012-03-25 14:03           ` Hans-Peter Nilsson
2012-03-25  7:40       ` Mike Frysinger
2012-03-25  7:54         ` Mike Frysinger
2012-03-25 14:26           ` Hans-Peter Nilsson
2012-03-24  5:39 ` [PATCH] sim: make sure to include strsignal prototype Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201203240012.05447.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hp@bitrange.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox