[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Assistance Request

From: Joel Sherrill
Subject: Re: Assistance Request
Date: Tue, 12 Feb 2008 11:16:05 -0600
User-agent: Thunderbird (X11/20071115)

Thanks.  That sped things up enormously and gets us to this
critical line of debug output:

spawning command powerpc-rtems4.9-run /home/joel/work-gnat/svn/b-gcc2-powerpc/gcc/testsuite/gcc/20010106-1.x0

Clearly, this isn't running my wrapper script. :(

I looked in basic-sim.exp and it allows you to override SIM on the
command line.  So I did this to my command which seems to work:

make check-gcc RUNTESTFLAGS="\
SIM=psim-4.9 \
RTEMS_MAKEFILE_PATH=/home/joel/work-gnat/423/bsp-install/powerpc-rtems4.9/psim \
--target=powerpc-rtems4.9 \
--target_board=rtems-powerpc-sim --all \

Since the execute.exp=2001* fragment you suggested ended with this:

               === gcc Summary ===

# of expected passes            626

Is there a way to make it just invoke a wrapper script for the simulator
without me overriding it on the command line?


Dave Korn wrote:
On 12 February 2008 16:35, Joel Sherrill wrote:

I think so.  I actually got an executable which
I could run but DejaGNU didn't know how to.
So that's half the battle. ;)

PASS: gcc.c-torture/execute/builtins/memset-chk.c compilation,  -O3
-fomit-frame-pointer -funroll-loops
core_find_mapping() - access to unmaped address, attach a default map to
handle this - addr=0x7c9c60 nr_bytes=0x4 processor=0x40017008 cia=0x14980

FAIL: gcc.c-torture/execute/builtins/memset-chk.c execution,  -O3
-fomit-frame-pointer -funroll-loops

But when I run it by hand...

$ psim-4.9 ./memset-chk.x5

*** EXIT code 0

How can I see what is invoked for the simulator run?

  Add lots of "-v" options to RUNTESTFLAGS.

Is there an easy way to skip to the executable tests?
I am tired of watching the compile only ones pass. :-D

  Add "execute.exp" to RUNTESTFLAGS.  You can also say e.g. something like
"execute.exp=2001*" to limit which of execute.exp's testcases are invoked.

I don't know that we will need this for RTEMS.

  I don't know what RTEMS does or doesn't have, so it might very well be
surplus to your requirements; I threw it into the mix just in case :)

Can't think of a witty .sigline today....

Joel Sherrill, Ph.D.             Director of Research & Development
address@hidden        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
  Support Available             (256) 722-9985

# Copyright (C) 1997-2008 Free Software
# Foundation, Inc.
# This file is part of DejaGnu.
# DejaGnu is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# DejaGnu is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# General Public License for more details.
# You should have received a copy of the GNU General Public License
# along with DejaGnu; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

# This is a list of toolchains that are supported on this board.
set_board_info target_install {powerpc-rtems4.9}

# Load the generic configuration for this board, This will define a basic
# set of routines needed by the tool to communicate with the board.
load_generic_config "sim"

# basic-sim.exp is a basic description for the standard Cygnus simulator.
load_base_board_description "basic-sim"

# The name of the simulator is "ppc".
setup_sim psim-4.9

# No multilib flags needed by default.
process_multilib_options ""

# The compiler used to build for this board. This has *nothing* to do
# with what compiler is tested if we're testing gcc.
set_board_info compiler  "[find_gcc]"

set_board_info cflags  "-B${RTEMS_MAKEFILE_PATH}/lib/ -specs bsp_specs -qrtems 
set_board_info ldflags ""

# The simulator isn't really remote.
set_board_info isremote 0

# We only have a small stack available to us
set_board_info gcc,stack_size 2048

# psim-4.9 is a wrapper script which handles the device tree
set_board_info sim "psim-4.9 "

# No support for signals on this target.
set_board_info gdb,nosignals 1

# The simulator doesn't return exit statuses and we need to indicate this.
set_board_info needs_status_wrapper 1

# Can't call functions from GDB.
# set_board_info gdb,cannot_call_functions 1

reply via email to

[Prev in Thread] Current Thread [Next in Thread]