Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: gdb-patches <gdb-patches@sources.redhat.com>, vinschen@redhat.com
Subject: Re: [PATCH]: testsuite/gdb.base/constvars.exp
Date: Tue, 25 Sep 2001 14:03:00 -0000	[thread overview]
Message-ID: <3BB0F122.3E45B3ED@cygnus.com> (raw)
In-Reply-To: <3BB0CB81.8385E123@redhat.com>

Fernando Nasser wrote:
> 
> Michael Snyder wrote:
> >
> > Corinna Vinschen wrote:
> > >
> > > Hi,
> > >
> > > I patched the test constvars.exp to get rid of the $gcc_compiled
> > > compile dependencies which result in XFAIL behaviour when the
> > > tests are compiled with GCC.  AFAICS, they aren't needed if just
> > > the tests are more correct.
> > >
> > > E.g., the testsuite expects strings like "unsigned long" while
> > > gdb may also emit "long unsigned" or "long unsigned int".
> > >
> > > The below patch cares for that.
> > >
> > > Corinna
> >
> > The test was originally submitted by HP, and probably
> > worked only with the HP compiler.  I like the idea of
> > extending itto work with GCC, but I wonder -- will this
> > work with stabs?  Or only with dwarf?
> >
> > And if it won't work with stabs -- do we care?
> >
> 
> Can someone please help us and try it with stabs?

OK, I've tried it.  Alas, it does not work.  And native Linux
still uses stabs, so that means we care.  ;-(  Sorry, Corinna.
It's a good change, but we need some kind of test that applies
the xfails for stabs and not for dwarf.

In the meantime, if you want to just check in the regular expression
changes, I'm sure that would be OK -- it would preserve your work.

Michael


  reply	other threads:[~2001-09-25 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 10:24 Corinna Vinschen
2001-09-25 10:43 ` Michael Snyder
2001-09-25 11:27   ` Fernando Nasser
2001-09-25 14:03     ` Michael Snyder [this message]
2001-09-26  9:15       ` Corinna Vinschen

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=3BB0F122.3E45B3ED@cygnus.com \
    --to=msnyder@cygnus.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vinschen@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