From: "Ijaz, Abdul B" <abdul.b.ijaz@intel.com>
To: Tom Tromey <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
"thiago.bauermann@linaro.org" <thiago.bauermann@linaro.org>,
"simark@simark.ca" <simark@simark.ca>
Subject: RE: [PATCH v4 1/3] gdb/testsuite: Fix indentation issues in gdb.dwarf2/dynarr-ptr.exp
Date: Fri, 12 Jan 2024 12:46:01 +0000 [thread overview]
Message-ID: <SA1PR11MB684647C551EF0CEBFD67AF47CB6F2@SA1PR11MB6846.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87cyu7rccz.fsf@tromey.com>
Hi Tom,
Thanks for the feedback.
Abdul> return -1
Abdul> }
Tom > This hunk doesn't look correct.
Second line is used differently in existing testsuite (e.g. with 4 spaces or tab + 2 spaces or more etc). I have used "4 spaces" in this patch for the splitted line. Will replace it with "Tab + 2 spaces" in V5 patch, hope it would be fine.
Best Regards,
Abdul Basit
-----Original Message-----
From: Tom Tromey <tom@tromey.com>
Sent: Thursday, January 11, 2024 6:47 PM
To: Ijaz, Abdul B <abdul.b.ijaz@intel.com>
Cc: gdb-patches@sourceware.org; thiago.bauermann@linaro.org; tom@tromey.com; simark@simark.ca
Subject: Re: [PATCH v4 1/3] gdb/testsuite: Fix indentation issues in gdb.dwarf2/dynarr-ptr.exp
>>>>> "Abdul" == Abdul Basit Ijaz <abdul.b.ijaz@intel.com> writes:
Abdul> From: "Ijaz, Abdul B" <abdul.b.ijaz@intel.com>
Abdul> ---
Abdul> gdb/testsuite/gdb.dwarf2/dynarr-ptr.exp | 138
Abdul> ++++++++++++------------
Abdul> 1 file changed, 69 insertions(+), 69 deletions(-)
Abdul> diff --git a/gdb/testsuite/gdb.dwarf2/dynarr-ptr.exp
Abdul> b/gdb/testsuite/gdb.dwarf2/dynarr-ptr.exp
Abdul> index 6e4a331eca8..26c64278103 100644
Abdul> --- a/gdb/testsuite/gdb.dwarf2/dynarr-ptr.exp
Abdul> +++ b/gdb/testsuite/gdb.dwarf2/dynarr-ptr.exp
Abdul> @@ -120,7 +120,7 @@ Dwarf::assemble $asm_file { # the compiler.
Abdul> if { [prepare_for_testing "failed to prepare" ${testfile} \
Abdul> - [list $srcfile $asm_file] {nodebug}] } {
Abdul> + [list $srcfile $asm_file] {nodebug}] } {
Abdul> return -1
Abdul> }
This hunk doesn't look correct.
The rest is ok though.
Tom
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-01-12 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 12:35 [PATCH v4 0/3] Dynamic properties of pointers Abdul Basit Ijaz
2024-01-04 12:35 ` [PATCH v4 1/3] gdb/testsuite: Fix indentation issues in gdb.dwarf2/dynarr-ptr.exp Abdul Basit Ijaz
2024-01-11 17:47 ` Tom Tromey
2024-01-12 12:46 ` Ijaz, Abdul B [this message]
2024-01-04 12:35 ` [PATCH v4 2/3] gdb, types: Resolve pointer types dynamically Abdul Basit Ijaz
2024-01-11 17:50 ` Tom Tromey
2024-01-12 17:42 ` Ijaz, Abdul B
2024-01-04 12:35 ` [PATCH v4 3/3] gdb, testsuite, fortran: Fix sizeof intrinsic for Fortran pointers Abdul Basit Ijaz
2024-01-11 17:51 ` [PATCH v4 0/3] Dynamic properties of pointers Tom Tromey
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=SA1PR11MB684647C551EF0CEBFD67AF47CB6F2@SA1PR11MB6846.namprd11.prod.outlook.com \
--to=abdul.b.ijaz@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=thiago.bauermann@linaro.org \
--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).