From: "Kempke, Nils-Christian via Gdb-patches" <gdb-patches@sourceware.org>
To: "George, Jini Susan" <JiniSusan.George@amd.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 18/18] gdb/testsuite: fixup common-block.exp for intel compilers
Date: Mon, 16 May 2022 07:59:58 +0000 [thread overview]
Message-ID: <CY4PR1101MB2071DDA76394978EFE4CA852B8CF9@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BY5PR12MB4965A82628A549CDE02D868390CF9@BY5PR12MB4965.namprd12.prod.outlook.com>
> -----Original Message-----
> From: George, Jini Susan <JiniSusan.George@amd.com>
> Sent: Monday, May 16, 2022 8:37 AM
> To: Kempke, Nils-Christian <nils-christian.kempke@intel.com>; gdb-
> patches@sourceware.org
> Subject: RE: [PATCH 18/18] gdb/testsuite: fixup common-block.exp for intel
> compilers
>
> [Public]
>
> Thanks for your patches, Nils, Cristian, Abdul, Felix -- these are extremely
> helpful. I have tried your patches with AMD AOCC flang and these boost up
> the fortran tests pass rate for flang also hugely.
>
Thanks for checking!
> A very minor suggestion:
>
> gdb.fortran/common-block.exp (lines 62 and 73): it would be great if you
> could add flang also along with ifx/ifort in the comments.
Done for v2.
Thanks,
Nils
> Thanks,
> Jini.
>
>
> >>-----Original Message-----
> >>From: Gdb-patches <gdb-patches-
> >>bounces+jigeorge=amd.com@sourceware.org> On Behalf Of Kempke,
> Nils-
> >>Christian via Gdb-patches
> >>Sent: Wednesday, May 11, 2022 9:02 PM
> >>To: Andrew Burgess <aburgess@redhat.com>; gdb-
> patches@sourceware.org
> >>Subject: RE: [PATCH 18/18] gdb/testsuite: fixup common-block.exp for
> intel
> >>compilers
> >>
> >>[CAUTION: External Email]
> >>
> >>> -----Original Message-----
> >>> From: Andrew Burgess <aburgess@redhat.com>
> >>> Sent: Wednesday, May 11, 2022 3:29 PM
> >>> To: Kempke, Nils-Christian <nils-christian.kempke@intel.com>; gdb-
> >>> patches@sourceware.org
> >>> Cc: JiniSusan.George@amd.com; Kempke, Nils-Christian <nils-
> >>> christian.kempke@intel.com>
> >>> Subject: Re: [PATCH 18/18] gdb/testsuite: fixup common-block.exp for
> >>> intel compilers
> >>>
> >>> Nils-Christian Kempke <nils-christian.kempke@intel.com> writes:
> >>>
> >>> > The order in which the variables in info common and info locals are
> >>> > displayed is compiler (and dwarf) dependent. While all symbols
> >>> > should be displayed the order is not fixed.
> >>> >
> >>> > I added a gdb_test_multiple that lets ifx and ifort pass in cases
> >>> > where only the order differs.
> >>> > ---
> >>> > gdb/testsuite/gdb.fortran/common-block.exp | 38
> >>> ++++++++++++++++++++--
> >>> > 1 file changed, 35 insertions(+), 3 deletions(-)
> >>> >
> >>> > diff --git a/gdb/testsuite/gdb.fortran/common-block.exp
> >>> b/gdb/testsuite/gdb.fortran/common-block.exp
> >>> > index ac39a4a575..fc38b8d772 100644
> >>> > --- a/gdb/testsuite/gdb.fortran/common-block.exp
> >>> > +++ b/gdb/testsuite/gdb.fortran/common-block.exp
> >>> > @@ -54,8 +54,27 @@ gdb_test "whatis fo_o$suffix" "No symbol
> >>> \"fo_o$suffix\" in current context."
> >>> > gdb_test "ptype fo_o$suffix" "No symbol \"fo_o$suffix\" in current
> >>> context."
> >>> > gdb_test "p fo_o$suffix" "No symbol \"fo_o$suffix\" in current
> context."
> >>> >
> >>> > -gdb_test "info locals" "ix_x = 11\r\niy_y = 22\r\niz_z = 33\r\nix =
> >>> > 1\r\niy =
> >>> 2\r\niz = 3" "info locals out"
> >>> > -gdb_test "info common" "Contents of F77 COMMON block
> >>> > 'fo_o':\r\nix_x
> >>> = 11\r\niy_y = 22\r\niz_z = 33\r\n\r\nContents of F77 COMMON block
> >>> 'foo':\r\nix = 1\r\niy = 2\r\niz = 3" "info common out"
> >>> > +gdb_test_multiple "info locals" "info locals out" {
> >>> > + # gfortran
> >>> > + -re "ix_x = 11\r\niy_y = 22\r\niz_z = 33\r\nix = 1\r\niy =
> >>> > +2\r\niz =
> >>> 3.*$gdb_prompt $" {
> >>> > + pass $gdb_test_name
> >>> > + }
> >>>
> >>> You can use:
> >>>
> >>> -re -wrap "ix_x = 11\r\niy_y = 22\r\niz_z = 33\r\nix = 1\r\niy = 2\r\niz =
> 3" {
> >>> ...
> >>> }
> >>>
> >>> to avoid having to add the $gdb_prompt in all of these tests.
> >>>
> >>> Thanks,
> >>> Andrew
> >>
> >>Thanks! That is more convenient indeed.
> >>Changed in v2.
> >>
> >>Nils
> >>
> >>Intel Deutschland GmbH
> >>Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
> >>Tel: +49 89 99 8853-0,
> >>https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fw
> ww.int
> >>el.de%2F&data=05%7C01%7CJiniSusan.George%40amd.com%7C386b
> 8a27
> >>b41c4c31135e08da3363612b%7C3dd8961fe4884e608e11a82d994e183d%7C
> 0%
> >>7C0%7C637878799180300920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM
> C4wL
> >>jAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7
> C%7C
> >>%7C&sdata=iahWHgSrYwg0K1Fb6%2Fm%2B49ZdPwxx%2F9sGZP1oU
> c09Z7
> >>4%3D&reserved=0
> >><https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fw
> ww.in
> >>tel.de%2F&data=05%7C01%7CJiniSusan.George%40amd.com%7C386
> b8a2
> >>7b41c4c31135e08da3363612b%7C3dd8961fe4884e608e11a82d994e183d%7
> C0
> >>%7C0%7C637878799180300920%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi
> MC4
> >>wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000
> %7C
> >>%7C%7C&sdata=iahWHgSrYwg0K1Fb6%2Fm%2B49ZdPwxx%2F9sGZP
> 1oUc
> >>09Z74%3D&reserved=0>
> >>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
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:[~2022-05-16 8:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 14:24 [PATCH 00/18] Fortran compiler identification and ifx testsuite support Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 01/18] gdb/testsuite: remove F77_FOR_TARGET support Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 02/18] gdb/testsuite: Use -module option for Intel Fortran compilers Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 03/18] gdb/testsuite: Fix fortran types for Intel compilers Nils-Christian Kempke via Gdb-patches
2022-05-11 9:49 ` Andrew Burgess via Gdb-patches
2022-05-11 9:57 ` Kempke, Nils-Christian via Gdb-patches
2022-05-10 14:24 ` [PATCH 04/18] gdb/testsuite: add local variable for passing 'getting_compiler_info' to gdb_compile Nils-Christian Kempke via Gdb-patches
2022-05-11 10:10 ` Andrew Burgess via Gdb-patches
2022-05-11 14:24 ` Kempke, Nils-Christian via Gdb-patches
2022-05-10 14:24 ` [PATCH 05/18] gdb/testsuite: add Fortran compiler identification to GDB Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 06/18] gdb/testsuite: rename intel next gen c/cpp compilers Nils-Christian Kempke via Gdb-patches
2022-05-11 11:23 ` Andrew Burgess via Gdb-patches
2022-05-11 14:28 ` Kempke, Nils-Christian via Gdb-patches
2022-05-10 14:24 ` [PATCH 07/18] gdb/testsuite: disable charset.exp for intel compilers Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 08/18] testsuite, fortran: make print-formatted.exp more robust Nils-Christian Kempke via Gdb-patches
2022-05-11 11:32 ` Andrew Burgess via Gdb-patches
2022-05-11 14:32 ` Kempke, Nils-Christian via Gdb-patches
2022-05-10 14:24 ` [PATCH 09/18] testsuite, fortran: add required external keyword Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 10/18] testsuite, fortran: add compiler dependent types to dynamic-ptype-whatis Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 11/18] testsuite, fortran: Add '-debug-parameters all' when compiling with ifx Nils-Christian Kempke via Gdb-patches
2022-05-11 11:56 ` Andrew Burgess via Gdb-patches
2022-05-11 14:36 ` Kempke, Nils-Christian via Gdb-patches
2022-05-10 14:24 ` [PATCH 12/18] testsuite/lib: add check_optional_entry for GDBInfoSymbols Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 13/18] testsuite, fortran: fix info-types for intel compilers Nils-Christian Kempke via Gdb-patches
2022-05-11 12:06 ` Andrew Burgess via Gdb-patches
2022-05-11 15:20 ` Kempke, Nils-Christian via Gdb-patches
2022-05-11 16:43 ` Kempke, Nils-Christian via Gdb-patches
2022-05-30 10:33 ` Andrew Burgess via Gdb-patches
2022-05-30 10:32 ` Andrew Burgess via Gdb-patches
2022-05-10 14:24 ` [PATCH 14/18] testsuite, fortran: Add type info of formal parameter for Intel compilers Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 15/18] testsuite, fortran: allow additional completions in module.exp Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 16/18] gdb, testsuite, fortran: fix double free in mixed-lang-stack.exp Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 17/18] gdb, testsuite, fortran: fixup mixed-lang-stack for Intel/LLVM compilers Nils-Christian Kempke via Gdb-patches
2022-05-10 14:24 ` [PATCH 18/18] gdb/testsuite: fixup common-block.exp for intel compilers Nils-Christian Kempke via Gdb-patches
2022-05-11 13:29 ` Andrew Burgess via Gdb-patches
2022-05-11 15:31 ` Kempke, Nils-Christian via Gdb-patches
2022-05-16 6:36 ` George, Jini Susan via Gdb-patches
2022-05-16 7:59 ` Kempke, Nils-Christian via Gdb-patches [this message]
2022-05-11 13:32 ` [PATCH 00/18] Fortran compiler identification and ifx testsuite support Andrew Burgess via Gdb-patches
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=CY4PR1101MB2071DDA76394978EFE4CA852B8CF9@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=JiniSusan.George@amd.com \
--cc=nils-christian.kempke@intel.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