From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: Andrew Burgess <aburgess@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2 03/16] gdb/testsuite: Fix fortran types for Intel compilers.
Date: Tue, 31 May 2022 14:48:47 +0000 [thread overview]
Message-ID: <CY4PR1101MB207114145FEFC499EFEA6B81B8DC9@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
In-Reply-To: <8735gpeqjk.fsf@redhat.com>
Hi Andrew,
thanks for reviewing.
I might have pushed this series by mistake - I saw your comment and somehow read it as a comment for the whole series (v2)..
Sorry for that .. We should likely revert it in this case and finish the reviewing first...
Best,
Nils
> -----Original Message-----
> From: Andrew Burgess <aburgess@redhat.com>
> Sent: Tuesday, May 31, 2022 4:16 PM
> To: Kempke, Nils-Christian <nils-christian.kempke@intel.com>; gdb-
> patches@sourceware.org
> Cc: JiniSusan.George@amd.com; Ijaz, Abdul B <abdul.b.ijaz@intel.com>
> Subject: Re: [PATCH v2 03/16] gdb/testsuite: Fix fortran types for Intel
> compilers.
>
> Nils-Christian Kempke via Gdb-patches <gdb-patches@sourceware.org>
> writes:
>
> > From: Felix Willgerodt <felix.willgerodt@intel.com>
> >
> > Newer Intel compilers emit their dwarf type name in a slightly different
> > format. Therefore, this needs adjustment to make more tests pass in the
> > Fortran testsuite.
> >
> > Co-authored-by: Abdul Basit Ijaz <abdul.b.ijaz@intel.com>
> > Co-authored-by: Nils-Christian Kempke <nils-christian.kempke@intel.com>
> > ---
> > gdb/testsuite/lib/fortran.exp | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
>
> LGTM.
>
> Thanks,
> Andrew
>
> >
> > diff --git a/gdb/testsuite/lib/fortran.exp b/gdb/testsuite/lib/fortran.exp
> > index a97c6eeb4e..9531d393a1 100644
> > --- a/gdb/testsuite/lib/fortran.exp
> > +++ b/gdb/testsuite/lib/fortran.exp
> > @@ -38,6 +38,8 @@ proc fortran_int4 {} {
> > return "integer"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "INTEGER\\(4\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "INTEGER\\*4"
> > } else {
> > return "unknown"
> > }
> > @@ -52,6 +54,8 @@ proc fortran_int8 {} {
> > return "integer\\*8"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "INTEGER\\(8\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "INTEGER\\*8"
> > } else {
> > return "unknown"
> > }
> > @@ -66,6 +70,8 @@ proc fortran_real4 {} {
> > return "real"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "REAL\\(4\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "REAL\\*4"
> > } else {
> > return "unknown"
> > }
> > @@ -80,6 +86,8 @@ proc fortran_real8 {} {
> > return "double precision"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "REAL\\(8\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "REAL\\*8"
> > } else {
> > return "unknown"
> > }
> > @@ -94,6 +102,8 @@ proc fortran_complex4 {} {
> > return "complex"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "COMPLEX\\(4\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "COMPLEX\\*8"
> > } else {
> > return "unknown"
> > }
> > @@ -108,6 +118,8 @@ proc fortran_complex8 {} {
> > return "double complex"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "COMPLEX\\(8\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "COMPLEX\\*16"
> > } else {
> > return "unknown"
> > }
> > @@ -122,6 +134,8 @@ proc fortran_complex16 {} {
> > return "quad complex"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "COMPLEX\\(16\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "COMPLEX\\*32"
> > } else {
> > return "unknown"
> > }
> > @@ -136,6 +150,8 @@ proc fortran_logical4 {} {
> > return "logical"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "LOGICAL\\(4\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "LOGICAL\\*4"
> > } else {
> > return "unknown"
> > }
> > @@ -150,6 +166,8 @@ proc fortran_character1 {} {
> > return "character"
> > } elseif {[test_compiler_info {icc-*}]} {
> > return "CHARACTER\\(1\\)"
> > + } elseif {[test_compiler_info {intel-*}]} {
> > + return "CHARACTER\\*1"
> > } else {
> > return "unknown"
> > }
> > --
> > 2.25.1
> >
> > 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
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-31 14:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 9:24 [PATCH v2 00/16] Fortran compiler identification and ifx testsuite support Nils-Christian Kempke
2022-05-31 9:24 ` [PATCH v2 03/16] gdb/testsuite: Fix fortran types for Intel compilers Nils-Christian Kempke
2022-05-31 14:15 ` Andrew Burgess
2022-05-31 14:48 ` Kempke, Nils-Christian [this message]
2022-05-31 9:24 ` [PATCH v2 04/16] gdb/testsuite: move getting_compiler_info to front of gdb_compile Nils-Christian Kempke
2022-05-31 16:00 ` Andrew Burgess
2022-05-31 9:24 ` [PATCH v2 06/16] gdb/testsuite: rename intel next gen c/cpp compilers Nils-Christian Kempke
2022-05-31 14:47 ` Andrew Burgess
2022-05-31 9:24 ` [PATCH v2 10/16] testsuite, fortran: Add '-debug-parameters all' when using ifx/ifort Nils-Christian Kempke
2022-05-31 16:03 ` Andrew Burgess
2022-05-31 9:24 ` [PATCH v2 12/16] testsuite, fortran: fix info-types for intel compilers Nils-Christian Kempke
2022-05-31 16:06 ` Andrew Burgess
2022-06-01 5:25 ` Tom de Vries
2022-06-01 9:21 ` Kempke, Nils-Christian
2022-06-03 6:53 ` Tom de Vries
2022-05-31 9:24 ` [PATCH v2 16/16] gdb/testsuite: fixup common-block.exp " Nils-Christian Kempke
2022-05-31 16:08 ` Andrew Burgess
2022-05-31 16:14 ` [PATCH v2 00/16] Fortran compiler identification and ifx testsuite support Andrew Burgess
2022-05-31 16:27 ` Kempke, Nils-Christian
2022-05-31 19:33 ` Tom de Vries
2022-06-01 4:54 ` Tom de Vries
2022-06-01 5:13 ` Tom de Vries
2022-06-01 6:44 ` Kempke, Nils-Christian
2022-06-01 7:10 ` Kempke, Nils-Christian
2022-06-01 7:32 ` Tom de Vries
2022-06-01 9:23 ` Kempke, Nils-Christian
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=CY4PR1101MB207114145FEFC499EFEA6B81B8DC9@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=nils-christian.kempke@intel.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@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).