From: Hans-Peter Nilsson <hp@bitrange.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: make sure to include strsignal prototype
Date: Fri, 23 Mar 2012 22:12:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1203231756080.353@dair.pair.com> (raw)
In-Reply-To: <201203231143.18540.vapier@gentoo.org>
On Fri, 23 Mar 2012, Mike Frysinger wrote:
> 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 fixed the ones that failed when i did `make check-sim`. wasn't ignoring the
> other ones, just didn't notice. i can fix them up too.
Yes; a grep will find them. Thanks.
> > 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/.
>
> i think last time i tried to build a cris toolchain it failed horribly so i
> gave up
Ok, I'll bite:
FWIW, my autotester for cris-elf+cris-sim is humming along with
*no* test-suite regressions for the gcc-4.7 branch@185744. For
gcc trunk@185744 there are *three* regressions since about 2007,
but all general, PR's open. Updates of sim, binutils newlib
happen automatically when there are no gcc regressions and
there's a clean update.
Then again, there are some general newbie obstacles when you
build a *-elf + *-sim toolchain from scratch for simulator
testing, though generally none target-specific... Well ok,
there's one caveat: you need dejagnu-1.5 or a debian-derived
dist (has all submitted baseboard files including the needed
cris-sim.exp) if you don't want to mess with local dejagnu
baseboard files.
brgds, H-P
next prev parent reply other threads:[~2012-03-23 22: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 [this message]
2012-03-23 22:43 ` Mike Frysinger
2012-03-24 5:34 ` Mike Frysinger
2012-03-24 4:12 ` Mike Frysinger
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=alpine.BSF.2.00.1203231756080.353@dair.pair.com \
--to=hp@bitrange.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.org \
/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