From: "Kempke, Nils-Christian via Gdb-patches" <gdb-patches@sourceware.org>
To: Andrew Burgess <aburgess@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 03/18] gdb/testsuite: Fix fortran types for Intel compilers.
Date: Wed, 11 May 2022 09:57:27 +0000 [thread overview]
Message-ID: <CY4PR1101MB20716AF66D744BEC76266F12B8C89@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87fslgl7pf.fsf@redhat.com>
> -----Original Message-----
> From: Andrew Burgess <aburgess@redhat.com>
> Sent: Wednesday, May 11, 2022 11:50 AM
> 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 03/18] 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.
>
> The change itself looks fine, but I don't understand the following:
>
> > There was not yet a way to handle the print for
> > variable length strings to this commit introduces fortran_integerN as
> > well.
>
> I suspect there's just a little context missing behind this.
Ah, yes. This is just a leftover in the commit message.. It should not be there anymore.
There was an obsolete change in this commit earlier, I removed it but it appears that
I forgot to remove the part from the commit message.
I changed it locally and removed that line.
> Thanks,
> Andrew
>
>
> >
> > 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(+)
> >
> > 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-11 9:57 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 [this message]
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
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=CY4PR1101MB20716AF66D744BEC76266F12B8C89@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=aburgess@redhat.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