Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Sat, 24 Mar 2012 06:49:00 -0000	[thread overview]
Message-ID: <alpine.BSF.2.00.1203240219320.13263@dair.pair.com> (raw)
In-Reply-To: <201203240212.04207.vapier@gentoo.org>

On Sat, 24 Mar 2012, Mike Frysinger wrote:
> > Did you "make check-sim RUNTESTFLAGS=--target_board=cris-sim"?
> > The warning message indicates the absence of that option or the
> > wrong baseboard.
>
> using those flags makes most run.  the linker segfaults when working on
> helloaout.c, so that can't be good:
>
> $ cris-elf-gcc ../../sim/testsuite/sim/cris/c/helloaout.c \
> 	-O2 -L/usr/local/src/gnu/sourceware/build/build-cris/ld -sim3 \
> 	-Wl,-mcrisaout -sim -Ttext=0 -lm -o helloaout.c.x -Bld
> collect2: ld terminated with signal 11 [Segmentation fault], core dumped

Ouch.  I'd be happy to process a ld PR for this, or I'll get to
it eventually.  Not that supporting a.out is of any particular
interest, but it shouldn't pollute the test-results.

> > (Arguably the *sim* test-suite should know set that option by
> > itself, but at least it's consistent with other runnable
> > dejagnu-based test-suites.)
>
> no other target needs this.

You mean "when you run the test-suite with a target compiler,
the only other sim target with C test-cases doesn't need this". :)
I see bfin had a few C test-cases added the last year, nice.

>  i did some work about two years ago specifically
> to avoid having to mess with dejagnu just to run `make check-sim`.

I guess you missed fixing CRIS then. :)
I'm not overexcited about the crusade making "sim" a special
case, when it works using the same dejagnu spell as anything
else.  So _no_ adding compiler flags to the individual
test-cases for the globally needed options.

> looks like the difference are just compiler flags ?

Linker flags, pointing to the right library, stuff like that...
See the baseboard file.  Different options for *-linux-gnu than
for *-elf though.  (Yes, the sim can run trivial cris*-linux-gnu
-static programs.)

brgds, H-P


  reply	other threads:[~2012-03-24  6:49 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
2012-03-24  5:53     ` Hans-Peter Nilsson
2012-03-24  6:12       ` Mike Frysinger
2012-03-24  6:49         ` Hans-Peter Nilsson [this message]
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.1203240219320.13263@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