public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mrs@wrs.com (Mike Stump)
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: small patch
Date: Wed, 14 Jan 1998 04:17:00 -0000	[thread overview]
Message-ID: <199801131847.KAA00320@kankakee.wrs.com> (raw)

sp is command in the target shell, meaning spawn, that command is used
by dejagnu to run testcases.  One feature of VxWorks target shell is
that you can replace builtins with new definitions, though replacing
sp with a global variable called sp isn't very useful.

This patch is reasonably safe, as we still test what it is the
testcase is trying to test.

> To: mrs@wrs.com (Mike Stump)
> cc: egcs@cygnus.com
> Date: Tue, 13 Jan 1998 00:48:16 -0700
> From: Jeffrey A Law <law@hurl.cygnus.com>

>   In message < 199801122240.OAA16601@kankakee.wrs.com >you write:
>   > Here is a small patch to avoid a failure on VxWorks:
>   > 
>   > Doing diffs in gcc/testsuite/g++.old-deja/g++.bugs:
>   > *** gcc/testsuite/g++.old-deja/g++.bugs/900520_05.C.~1~	Mon Jan 12 13:5
>   > 3:27 1998
>   > --- gcc/testsuite/g++.old-deja/g++.bugs/900520_05.C	Mon Jan 12 13:54:48 199
>   > 8
>   > *************** struct struct_0 {
>   > *** 8,14 ****
>   >   };
>   >   
>   >   char *cp;
>   > ! struct_0 *sp;
>   >   
>   >   void test0 ()
>   >   {
>   > --- 8,14 ----
>   >   };
>   >   
>   >   char *cp;
>   > ! static struct_0 *sp;
>   >   
>   >   void test0 ()
>   >   {
>   > --------------
> Huh?  Something's rather bogus here.  Why does adding a static help
> VxWorks?

             reply	other threads:[~1998-01-14  4:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-14  4:17 Mike Stump [this message]
1998-01-14  4:17 ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1998-03-29  5:14 Mike Stump
1998-01-16 20:09 Mike Stump
1998-01-17 23:57 ` Jeffrey A Law
1998-01-15 16:06 Mike Stump
1998-01-12 14:41 Mike Stump
1998-01-13  4:31 ` Jeffrey A Law

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=199801131847.KAA00320@kankakee.wrs.com \
    --to=mrs@wrs.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.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).