From: Mark Wielaard <mjw@redhat.com>
To: Joel Brobecker <brobecker@adacore.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 11:15:00 -0000 [thread overview]
Message-ID: <1393499740.8933.215.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <1393497031.8933.208.camel@bordewijk.wildebeest.org>
On Thu, 2014-02-27 at 11:30 +0100, Mark Wielaard wrote:
> 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?
It was pointed out on irc that it would be helpful to mention the
gcc-gnat version used and the actual failures from gdb.sum.
GNAT 4.4.7 20120313 (Red Hat 4.4.7-4)
FAIL: gdb.ada/aliased_array.exp: print bt
FAIL: gdb.ada/array_bounds.exp: print table'first
FAIL: gdb.ada/array_bounds.exp: print table'last
FAIL: gdb.ada/arrayidx.exp: print e_one_two_three, indexes off
FAIL: gdb.ada/arrayidx.exp: print r_two_three, indexes off
FAIL: gdb.ada/arrayidx.exp: print p_one_two_three, indexes off
FAIL: gdb.ada/arrayidx.exp: print e_one_two_three
FAIL: gdb.ada/arrayidx.exp: print r_two_three
FAIL: gdb.ada/arrayidx.exp: print p_one_two_three
FAIL: gdb.ada/dyn_loc.exp: info locals
FAIL: gdb.ada/enum_idx_packed.exp: print full
FAIL: gdb.ada/enum_idx_packed.exp: print full'first
FAIL: gdb.ada/iwide.exp: print sp_access.all
FAIL: gdb.ada/iwide.exp: print dp_access.all
FAIL: gdb.ada/mi_interface.exp: compilation foo.adb
FAIL: gdb.ada/null_array.exp: ptype my_table
FAIL: gdb.ada/optim_drec.exp: print z
FAIL: gdb.ada/packed_tagged.exp: print x
FAIL: gdb.ada/taft_type.exp: print w.e.all
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print My_Object with null Ptr
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print My_Object.Ptr when null
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print My_P_Object with null Ptr
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print My_P_Object.Ptr when null
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print my_object after setting Ptr
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print My_P_Object.Ptr when no longer null
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print my_p_object after setting Ptr
FAIL: gdb.ada/unc_arr_ptr_in_var_rec.exp: print My_P_Object.Ptr when no longer null
FAIL: gdb.ada/variant_record_packed_array.exp: print adress content
FAIL: gdb.ada/whatis_array_val.exp: print full
next prev parent reply other threads:[~2014-02-27 11:15 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 [this message]
2014-02-27 14:29 ` Joel Brobecker
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=1393499740.8933.215.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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