Re: [PATCH] sim: make sure to include strsignal prototype

[Mike Frysinger <vapier@gentoo.org>]

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

On Saturday 24 March 2012 02:48:45 Hans-Peter Nilsson wrote:
> 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.

http://sourceware.org/bugzilla/show_bug.cgi?id=13900

> >  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. :)

not really ... the code fixed up was common code to automatically select the 
locally compiled `run` binary if no sim was specified

> 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.

i don't know what you're referring to at all here

> > 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.

i don't think it's unreasonable for the cris sim exp to set up sane defaults 
based on the target.  you know if the sim was configured for *-elf or *-linux-
gnu by default.

> (Yes, the sim can run trivial cris*-linux-gnu -static programs.)

and the Blackfin sim can handle static or dynamic Linux userland code in 
addition to booting a Linux kernel or just running newlib/libgloss apps.

$ echo 'main(){puts("HI");}' | bfin-linux-uclibc-gcc -x c - -o a.out -static
$ bfin-elf-run --env user ./a.out 
HI
-mike

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