Hi Janis
> The GCC testsuite support does some really ugly things to support
> functionality that is not available in DejaGnu. For example, it
> uses upvar to reference DejaGnu local variables and overrides
> several DejaGnu procs. I'd like to propose several changes to
> DejaGnu that would even
Hi,
The other source of noise in RTEMS test results
are the profiling tests. Again the latest
powerpc-rtems results:
http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg01477.html
A typical noise entry is:
FAIL: gcc.dg/matrix/transpose-6.c compilation, -fprofile-generate -O3
UNRESOLVED: gcc.dg/
Hi,
Janis wanted a recap on this list. The thread
starts here:
http://gcc.gnu.org/ml/gcc/2008-04/msg00587.html
And this is the last message in the thread which
sums up the expert views:
http://gcc.gnu.org/ml/gcc/2008-04/msg00708.html
The latest powerpc-rtems4.10 GCC test results
are here:
h
Janis Johnson wrote:
The GCC testsuite support does some really ugly things to support
functionality that is not available in DejaGnu. For example, it uses
upvar to reference DejaGnu local variables and overrides several DejaGnu
procs. I'd like to propose several changes to DejaGnu that would
e
On Wed, 2008-12-17 at 15:36 -0600, Joel Sherrill wrote:
> Janis Johnson wrote:
> > The GCC testsuite support does some really ugly things to support
> > functionality that is not available in DejaGnu. For example, it uses
> > upvar to reference DejaGnu local variables and overrides several DejaGnu
Janis Johnson wrote:
> The GCC testsuite support does some really ugly things to support
> functionality that is not available in DejaGnu. For example, it uses
I think that could be called an understatement. :-) In the begging,
all testsuites actually lived in DejaGnu, so there was tighter
int
Daniel Jacobowitz suggested back in April that DejaGnu apply a Debian
patch to use the environment variable DEJAGNU_TIMEOUT to override the
default timeout value:
http://lists.gnu.org/archive/html/dejagnu/2008-04/msg1.html
The GCC testsuite now has support for using timeout values from test
The GCC testsuite has local support for restricting tests to particular
targets or for marking a test as XFAIL. In order to do this the local
support uses upvar to access and modify dg-do-what, a local variable in
the DejaGnu procedure dg-test. This is always done one call away from
dg-test so i
In several places the GCC testsuite needs to know the name of the
current test. Sometimes it uses it to report unresolved test steps and
sometimes it uses it to construct the name of a generated file, such as
the assembly file or a debugging dump.
GCC gets the name of the current test by using up
The GCC testsuite support does some really ugly things to support
functionality that is not available in DejaGnu. For example, it uses
upvar to reference DejaGnu local variables and overrides several DejaGnu
procs. I'd like to propose several changes to DejaGnu that would
eventually allow GCC to
I'm nearly finished with a CGEN simulator and tool chain port.
Just a couple of things left.
The most annoying of which is trying to get the configuration of
dejagnu for this simulator.
runtest --version says
Expect version is 5.42.0
Tcl version is8.4
Framework vers
I'm nearly finished with my CGEN simulator and tool chain port.
Just a couple of things left.
The most annoying of which is trying to get the configuration of
dejagnu for this simulator.
I would like it to use a dejagnu/baseboards/MYCPU-sim.exp in my
source tree, but it seems determined
12 matches
Mail list logo
