Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mark Wielaard <mjw@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/DWARF] Set enum type "flag_enum" and "unsigned" flags at type creation.
Date: Thu, 27 Feb 2014 14:29:00 -0000	[thread overview]
Message-ID: <20140227142904.GP4348@adacore.com> (raw)
In-Reply-To: <1393497031.8933.208.camel@bordewijk.wildebeest.org>

> Sorry, I didn't have gcc-gnat installed and so missed this. I have it
> installed now. BTW. Are there any overviews of what are expected
> results? For make check RUNTESTFLAGS='--directory gdb.ada' I get:
> 
> 		=== gdb Summary ===
> 
> # of expected passes            490
> # of unexpected failures        29
> # of unexpected successes       8
> # of expected failures          2
> # of known failures             1
> # of unsupported tests          3
> 
> Is that reasonable? The amount of failures seems a bit high. The
> testsuite is not supposed to be (near) zero-fail?

IMO, it depends too much on the compiler used. Although we try to
actively contribute all our GCC patches the same way we contribute
our GDB patches, there are always a few that keep missing in the FSF
tree. To have near-clean results, I think you would need to use our
latest GPL'ed binary (we publish one each year). That's why you'll
see me generate C testcases as much as possible, even if the problem
is only showing up in Ada code.

Regardless of that, I don't expect anyone but me to really set their
environment up towards clean results. As long as it's not regressing
in your environment, I'm happy taking take care of accidental
regressions.

-- 
Joel


  parent reply	other threads:[~2014-02-27 14:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  8:09 Joel Brobecker
2014-02-10 14:29 ` Joel Brobecker
2014-02-17 20:20 ` Joel Brobecker
2014-02-19 14:34 ` Mark Wielaard
2014-02-19 15:18   ` Mark Wielaard
2014-02-21  9:21     ` Joel Brobecker
2014-02-25 14:32       ` Mark Wielaard
2014-02-26 18:32     ` Joel Brobecker
2014-02-26 18:58       ` Joel Brobecker
2014-02-27 10:30       ` Mark Wielaard
2014-02-27 11:15         ` Mark Wielaard
2014-02-27 14:29         ` Joel Brobecker [this message]
2014-02-26 18:42 ` pushed: " Joel Brobecker

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=20140227142904.GP4348@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mjw@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