Re: c++/1752: libiberty/demangle testsuite failures on i686-pc-cygwin

Re: c++/1752: libiberty/demangle testsuite failures on i686-pc-cygwin

[billingd]

Synopsis: libiberty/demangle testsuite failures on i686-pc-cygwin

State-Changed-From-To: feedback->closed
State-Changed-By: billingd
State-Changed-When: Mon Oct 29 22:33:56 2001
State-Changed-Why:
    cygwin ash (/bin/sh) problem.
    Fixed in ash-20011018-1

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=1752&database=gcc

Re: c++/1752 libiberty/demangle testsuite failures on i686-pc-cygwin

[Tim Prince]

The following reply was made to PR c++/1752; it has been noted by GNATS.

From: "Tim Prince" <tprince@computer.org>
To: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>,
        <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <rodrigc@gcc.gnu.org>,
        <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>
Cc: <christian.jonsson@foi.se>
Subject: Re: c++/1752 libiberty/demangle testsuite failures on i686-pc-cygwin 
Date: Wed, 15 Aug 2001 19:37:10 -0700

 ----- Original Message -----
 From: "Billinghurst, David (CRTS)"
 <David.Billinghurst@riotinto.com>
 To: <gcc-gnats@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>;
 "Billinghurst, David (CRTS)"
 <David.Billinghurst@riotinto.com>; <rodrigc@gcc.gnu.org>;
 <gcc-bugs@gcc.gnu.org>; <nobody@gcc.gnu.org>
 Cc: <christian.jonsson@foi.se>
 Sent: Wednesday, August 15, 2001 6:37 PM
 Subject: re: c++/1752 libiberty/demangle testsuite failures on
 i686-pc-cygwin
 
 
 > This is still a problem.  I now believe the problem is a
 cygwin shell issue.
 > The tests that fail are exactly those that have a $ in the
 name.
 >
 > The test (from the Makefile) is
 >
 > # Run some tests of the demangler.
 > check-cplus-dem: test-filter $(srcdir)/demangle-expected
 >         $(SHELL) $(srcdir)/regress-demangle
 $(srcdir)/demangle-expected
 >
 > Run by hand
 >
 > $ /bin/sh
 /usr/local/src/gcc-3.0/libiberty/testsuite/regress-demangle
 > /usr/local/src/gcc-3.0/libiberty/testsuite/demangle-expected
 >
 > I get the results previosuly reported.
 >
 > Using bash all the test pass
 >
 > $ /bin/bash
 /usr/local/src/gcc-3.0/libiberty/testsuite/regress-demangle
 > /usr/local/src/gcc-3.0/libiberty/testsuite/demangle-expected
 > All 645 tests passed
 >
 OK, we could replace /bin/sh by a copy of bash (temporarily) ,
 if we don't mind the extra time required to run the entire
 test suite.
 

re: c++/1752 libiberty/demangle testsuite failures on i686-pc-cygwin

[Billinghurst, David (CRTS)]

The following reply was made to PR c++/1752; it has been noted by GNATS.

From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>,
   "'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>,
   "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>,
   "'rodrigc@gcc.gnu.org'" <rodrigc@gcc.gnu.org>,
   "'gcc-bugs@gcc.gnu.org'"
	 <gcc-bugs@gcc.gnu.org>,
   "'nobody@gcc.gnu.org'" <nobody@gcc.gnu.org>
Cc: "'christian.jonsson@foi.se'" <christian.jonsson@foi.se>
Subject: re: c++/1752 libiberty/demangle testsuite failures on i686-pc-cyg
	win 
Date: Thu, 16 Aug 2001 01:37:01 -0000

 This is still a problem.  I now believe the problem is a cygwin shell issue.
 The tests that fail are exactly those that have a $ in the name.
 
 The test (from the Makefile) is
 
 # Run some tests of the demangler.
 check-cplus-dem: test-filter $(srcdir)/demangle-expected
         $(SHELL) $(srcdir)/regress-demangle $(srcdir)/demangle-expected
 
 Run by hand
 
 $ /bin/sh  /usr/local/src/gcc-3.0/libiberty/testsuite/regress-demangle
 /usr/local/src/gcc-3.0/libiberty/testsuite/demangle-expected
 
 I get the results previosuly reported.
 
 Using bash all the test pass
 
 $ /bin/bash  /usr/local/src/gcc-3.0/libiberty/testsuite/regress-demangle
 /usr/local/src/gcc-3.0/libiberty/testsuite/demangle-expected
 All 645 tests passed
 
 

Re: c++/1752: libiberty/demangle testsuite failures on i686-pc-cygwin

[rodrigc]

Synopsis: libiberty/demangle testsuite failures on i686-pc-cygwin

State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Sun Aug 12 13:10:49 2001
State-Changed-Why:
    I do not see these test failures in the current
    gcc in CVS.  Can you obtain a newer gcc snapshot
    and try again?

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1752&database=gcc