From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
Cc: simark@simark.ca, tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/4] Dynamic properties of pointers
Date: Mon, 02 Oct 2023 21:17:57 -0300 [thread overview]
Message-ID: <874jj8eeyy.fsf@linaro.org> (raw)
In-Reply-To: <20230904222956.15203-1-abdul.b.ijaz@intel.com>
Abdul Basit Ijaz via Gdb-patches <gdb-patches@sourceware.org> writes:
> Bernhard Heckel (1):
> gdb, types: Resolve pointer types dynamically
>
> Nils-Christian Kempke (3):
> gdb, testsuite: handle icc and icpc deprecated remarks
> gdb, intel-classic-compilers, testsuite: workaround icc/icpc/ifort
> pointer/reference DWARF
> gdb, testsuite, fortran: Fix sizeof intrinsic for ifort Fortran
> pointers
>
> gdb/eval.c | 9 +
> gdb/gdbtypes.c | 101 +++++++++-
> gdb/gdbtypes.h | 5 +
> gdb/testsuite/gdb.cp/vla-cxx.cc | 4 +
> gdb/testsuite/gdb.cp/vla-cxx.exp | 15 ++
> gdb/testsuite/gdb.dwarf2/dynarr-ptr.exp | 16 +-
> .../icc-ifort-pointers-and-references.c | 38 ++++
> .../icc-ifort-pointers-and-references.exp | 169 +++++++++++++++++
> .../gdb.fortran/pointer-to-pointer.exp | 2 +-
> gdb/testsuite/gdb.fortran/pointers.exp | 173 ++++++++++++++++++
> gdb/testsuite/gdb.fortran/pointers.f90 | 29 +++
> gdb/testsuite/gdb.fortran/sizeof.exp | 115 ++++++++++++
> gdb/testsuite/gdb.fortran/sizeof.f90 | 108 +++++++++++
> gdb/testsuite/lib/gdb.exp | 14 +-
> gdb/valprint.c | 40 +++-
> 15 files changed, 812 insertions(+), 26 deletions(-)
> create mode 100644 gdb/testsuite/gdb.dwarf2/icc-ifort-pointers-and-references.c
> create mode 100644 gdb/testsuite/gdb.dwarf2/icc-ifort-pointers-and-references.exp
> create mode 100644 gdb/testsuite/gdb.fortran/pointers.exp
> create mode 100644 gdb/testsuite/gdb.fortran/sizeof.exp
> create mode 100644 gdb/testsuite/gdb.fortran/sizeof.f90
I ran the tests added or modified by this patch series on aarch64-linux
with gfortran 11.3.0 (from Ubuntu 22.04) and all tests pass:
Tested-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
--
Thiago
prev parent reply other threads:[~2023-10-03 0:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 22:29 Abdul Basit Ijaz
2023-09-04 22:29 ` [PATCH v3 1/4] gdb, testsuite: handle icc and icpc deprecated remarks Abdul Basit Ijaz
2023-10-03 0:04 ` Thiago Jung Bauermann
2023-09-04 22:29 ` [PATCH v3 2/4] gdb, types: Resolve pointer types dynamically Abdul Basit Ijaz
2023-10-03 0:07 ` Thiago Jung Bauermann
2023-10-10 19:45 ` Tom Tromey
2024-01-03 21:06 ` Ijaz, Abdul B
2024-01-03 21:06 ` Ijaz, Abdul B
2023-10-10 19:49 ` Tom Tromey
2024-01-03 21:31 ` Ijaz, Abdul B
2023-09-04 22:29 ` [PATCH v3 3/4] gdb, intel-classic-compilers, testsuite: workaround icc/icpc/ifort pointer/reference DWARF Abdul Basit Ijaz
2023-10-03 0:09 ` Thiago Jung Bauermann
2023-10-10 19:52 ` Tom Tromey
2024-01-03 21:15 ` Ijaz, Abdul B
2023-09-04 22:29 ` [PATCH v3 4/4] gdb, testsuite, fortran: Fix sizeof intrinsic for ifort Fortran pointers Abdul Basit Ijaz
2023-10-03 0:16 ` Thiago Jung Bauermann
2023-09-27 21:11 ` [PING][PATCH v3 0/4] Dynamic properties of pointers Ijaz, Abdul B
2023-10-03 0:17 ` Thiago Jung Bauermann [this message]
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=874jj8eeyy.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=abdul.b.ijaz@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).