public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Non bit-packed packed arrays as variable-length fields
Date: Fri, 15 May 2015 21:25:00 -0000	[thread overview]
Message-ID: <931e5bc3e19d1e279fc28c5cf5571f812c79b8d3@kwanyin> (raw)

*** TEST RESULTS FOR COMMIT 931e5bc3e19d1e279fc28c5cf5571f812c79b8d3 ***

Author: Jerome Guitton <guitton@adacore.com>
Branch: master
Commit: 931e5bc3e19d1e279fc28c5cf5571f812c79b8d3

Non bit-packed packed arrays as variable-length fields
In the case of non bit-packed arrays, GNAT does not generate its
traditional XP encoding; it is not needed. However, it still generates
the so-called "implementation type" with a P suffix. This
implementation type shall be skipped when looking for other
descriptive types such as XA encodings for variable-length
fields.

Note also that there may be an intermediate typedef between the
implementation type and its XA description. It shall be skipped
as well.

gdb/ChangeLog:

        Jerome Guitton  <guitton@adacore.com>
	* ada-lang.c (find_parallel_type_by_descriptive_type):
	Go through typedefs during lookup.
	(to_fixed_array_type): Add support for non-bit packed arrays
	as variable-length fields.

gdb/testsuite/ChangeLog:

        * gdb.ada/byte_packed_arr: New testcase.


             reply	other threads:[~2015-05-15 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 21:25 sergiodj+buildbot [this message]
2015-05-15 21:25 ` Failures on Fedora-ppc64be-native-gdbserver-m64, branch master sergiodj+buildbot
2015-05-15 21:37 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot
2015-05-15 21:44 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-05-15 21:56 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2015-05-15 22:20 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2015-05-16  3:43 ` Failures on Fedora-i686, " sergiodj+buildbot
2015-05-16  4:16 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2015-05-16  4:47 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-05-16  5:32 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2015-05-16 10:43 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2015-05-16 12:04 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot

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=931e5bc3e19d1e279fc28c5cf5571f812c79b8d3@kwanyin \
    --to=sergiodj+buildbot@redhat.com \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).