public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Hubicka <jh@suse.cz>
To: Roger Sayle <roger@www.eyesopen.com>
Cc: Jan Hubicka <jh@suse.cz>, gcc-patches@gcc.gnu.org
Subject: Re: gcc.dg/i386-local2.c breaks testsuite on x86
Date: Fri, 07 Mar 2003 16:39:00 -0000	[thread overview]
Message-ID: <20030307163931.GA7871@kam.mff.cuni.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0303070746220.22062-100000@www.eyesopen.com>

> 
> Hi Jan,
> 
> It looks like your recent testcase, gcc.dg/i386-local2.c breaks
> the gcc testsuite on i686-pc-linux-gnu.  For example, see
> http://gcc.gnu.org/ml/gcc-testresults/2003-03/msg00405.html
> 
> Specifically this bit of that posting:
> 
> FAIL: gcc.dg/i386-local.c (test for excess errors)
> ERROR: gcc.dg/i386-local.c: error executing dg-final: couldn't open
> "i386-local.s": no such file or directory
> UNRESOLVED: gcc.dg/i386-local.c: error executing dg-final: couldn't open
> "i386-local.s": no such file or directory
> ERROR: (DejaGnu) proc "re" does not exist.
> 
> The syntax of the DejaGNU directive at the start of the file, i.e.
> 
> /* { dg-final { scan-assembler-not "sub.*[re]sp" } } */
> 
> is being misinterpreted, so that the "re" in the regular expression
> is considered a Tcl procedure.  This terminates the gcc testsuite
> prematurely, effectively creating ~400 regressions on the gcc tests.
> You'll notice there's only ~17,000 passes for gcc in the above e-mail
> rather then the expected ~21,000.

Strange, there is no such problem in my runs.  I will fix it by
replacing re by .

Honza
> 
> This might be caused by different versions of DejaGNU, if your
> testing can't reproduce it.  I'm currently running Tcl 8.3, expect
> 5.33.0 and dejagnu 1.4.0.  I tried upgrading to dejagnu 1.4.3 but
> that doesn't build/install cleanly on RedHat 7.2.
> 
> 
> Given the otehr bootstrap failures caused by this commit, might it
> be that you applied an earlier version of your patch?  You'll notice
> that there are also non-fatal errors from your gcc.dg/i386-local.c
> change.
> 
> Many thanks in advance,
> 
> Roger
> --
> Roger Sayle,                         E-mail: roger@eyesopen.com
> OpenEye Scientific Software,         WWW: http://www.eyesopen.com/
> Suite 1107, 3600 Cerrillos Road,     Tel: (+1) 505-473-7385
> Santa Fe, New Mexico, 87507.         Fax: (+1) 505-473-0833

      reply	other threads:[~2003-03-07 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07 15:44 Roger Sayle
2003-03-07 16:39 ` Jan Hubicka [this message]

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=20030307163931.GA7871@kam.mff.cuni.cz \
    --to=jh@suse.cz \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=roger@www.eyesopen.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).