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 3/4] gdb, intel-classic-compilers, testsuite: workaround icc/icpc/ifort pointer/reference DWARF
Date: Mon, 02 Oct 2023 21:09:09 -0300 [thread overview]
Message-ID: <87cyxwefdm.fsf@linaro.org> (raw)
In-Reply-To: <20230904222956.15203-4-abdul.b.ijaz@intel.com>
Hello,
Abdul Basit Ijaz via Gdb-patches <gdb-patches@sourceware.org> writes:
> ---
> gdb/gdbtypes.c | 94 +++++++++-
> gdb/gdbtypes.h | 5 +
> .../icc-ifort-pointers-and-references.c | 38 ++++
> .../icc-ifort-pointers-and-references.exp | 169 ++++++++++++++++++
> gdb/testsuite/gdb.fortran/pointers.exp | 86 +++++++--
> gdb/valprint.c | 34 ++++
> 6 files changed, 409 insertions(+), 17 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
This patch reorganizes the code a bit, but still uses the same approach
as v2. Have you tried implementing the approach suggested by Tom Tromey
in https://inbox.sourceware.org/gdb-patches/87fscoepd5.fsf@tromey.com/ ?
> diff --git a/gdb/testsuite/gdb.dwarf2/icc-ifort-pointers-and-references.c b/gdb/testsuite/gdb.dwarf2/icc-ifort-pointers-and-references.c
> new file mode 100644
> index 00000000000..0c0be751833
> --- /dev/null
> +++ b/gdb/testsuite/gdb.dwarf2/icc-ifort-pointers-and-references.c
> @@ -0,0 +1,38 @@
> +/* This testcase is part of GDB, the GNU debugger.
> +
> + Copyright 2021-2023 Free Software Foundation, Inc.
The copyright starts in 2023.
> +
> + This program is free software; you can redistribute it and/or modify
> + it under the terms of the GNU General Public License as published by
> + the Free Software Foundation; either version 3 of the License, or
> + (at your option) any later version.
> +
> + This program is distributed in the hope that it will be useful,
> + but WITHOUT ANY WARRANTY; without even the implied warranty of
> + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + GNU General Public License for more details.
> +
> + You should have received a copy of the GNU General Public License
> + along with this program. If not, see <http://www.gnu.org/licenses/>. */
--
Thiago
next prev parent reply other threads:[~2023-10-03 0:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 22:29 [PATCH v3 0/4] Dynamic properties of pointers 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 [this message]
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 ` [PATCH " Thiago Jung Bauermann
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=87cyxwefdm.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).