Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Fernando Nasser <fnasser@redhat.com>,
	gdb-patches@sources.redhat.com,
	Daniel Jacobowitz <drow@mvista.com>
Subject: Re: [rfa] store.exp failures
Date: Fri, 06 Dec 2002 19:32:00 -0000	[thread overview]
Message-ID: <ro1znri8vfq.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3DF11CD6.8010407@redhat.com>

On Fri, 06 Dec 2002 16:55:34 -0500, Andrew Cagney <ac131313@redhat.com> said:

> On a powerpc:

> Running /home/scratch/GDB/src/gdb/testsuite/gdb.base/store.exp ...

>                  === gdb Summary ===

> # of expected passes            204

> ac131313@nettle$ gcc --version
> 2.95.3

> And on a Red Hat 7,2 system:

> Running /home/cagney/GDB/src/gdb/testsuite/gdb.base/store.exp ...

>                  === gdb Summary ===

> # of expected passes            204

> cagney@torrens$ gcc --version
> 2.96

Yeah, 2.96 passes for me, too.  Who knows what's going on with
i686-gnu-linux 2.95.3, then.

> BTW, what makes you think the test is delicate?  The code is valid C
> and the command:

> 	(gdb) set variable u = s_1

> is valid in GDB's CLI.  If it doesn't work, its a bug.

Actually, I was misinterpreting the following comment at the top of
store.c:

/* Check that GDB can correctly update a value, living in a register,
   in the target.  This pretty much relies on the compiler taking heed
   of requests for values to be stored in registers.  */

But I suppose that, even if the compiler doesn't pay attention to
'register' requests, the tests should stil work fine, they just won't
test what they're supposed to.  So 'delicate' is definitely the wrong
word.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2002-12-07  1:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 15:32 David Carlton
2002-12-05 16:19 ` Fernando Nasser
2002-12-06 11:37   ` David Carlton
2002-12-06 11:58     ` Andrew Cagney
2002-12-06 12:15       ` David Carlton
2002-12-06 14:08         ` Andrew Cagney
2002-12-06 19:32           ` David Carlton [this message]
2002-12-06 15:54         ` Andrew Cagney

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=ro1znri8vfq.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.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