public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: Nils-Christian Kempke <nils-christian.kempke@intel.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v3 00/11] Improve Fortran intrinsic types and procedures
Date: Mon, 25 Apr 2022 13:52:19 +0100	[thread overview]
Message-ID: <b262a336-02cc-a555-3857-00e55e4e2026@arm.com> (raw)
In-Reply-To: <20220411081859.459151-1-nils-christian.kempke@intel.com>

Hi,

On 4/11/22 09:18, Nils-Christian Kempke via Gdb-patches wrote:
> Hi,
> 
> please find attached v3 of the series.
> 
> V1 can be found here
> 
> https://sourceware.org/pipermail/gdb-patches/2022-March/186473.html
> 
> V2 here
> 
> https://sourceware.org/pipermail/gdb-patches/2022-April/187655.html
> 
> Changes since V2:
> 
> 	- [Patch 11/11]: Fixed Texinfo issues.
> 
> 
> Thanks!
> 
> Nils
> 
> 
> Nils-Christian Kempke (11):
>    gdb/f-lang: add Integer*1 to Fortran builtin types
>    gdb/f-lang: remove hidden ^L characters
>    gdb/fortran: fix complex type in Fortran builtin types
>    gdb/fortran: reformat build_fortran_types in f-lang.c
>    gdb/fortran: change default logical type to builtin_logical
>    gdb/fortran: clean-up Fortran intrinsic types
>    gdb/fortran: Change GDB print for fortran default types
>    gdb/fortran: rename f77_keywords to f_keywords
>    gdb/fortran: rewrite intrinsic handling and add some missing overloads
>    gdb/fortran/testsuite: add complex from integers test
>    gdb/doc: add section about Fortran intrinsic functions and types
> 
>   gdb/doc/gdb.texinfo                         | 143 ++++++-
>   gdb/f-exp.h                                 | 182 +++++++--
>   gdb/f-exp.y                                 | 397 ++++++++++++++------
>   gdb/f-lang.c                                | 267 +++++++++----
>   gdb/f-lang.h                                |   7 +-
>   gdb/std-operator.def                        |  10 +-
>   gdb/testsuite/gdb.fortran/complex.exp       |  10 +-
>   gdb/testsuite/gdb.fortran/complex.f90       |   7 +-
>   gdb/testsuite/gdb.fortran/intrinsics.exp    |  46 ++-
>   gdb/testsuite/gdb.fortran/lbound-ubound.F90 |  49 ++-
>   gdb/testsuite/gdb.fortran/lbound-ubound.exp |  29 +-
>   gdb/testsuite/gdb.fortran/size.exp          |  84 ++++-
>   gdb/testsuite/gdb.fortran/size.f90          | 213 ++++++++---
>   gdb/testsuite/gdb.fortran/type-kinds.exp    |   2 +
>   gdb/testsuite/gdb.fortran/types.exp         |  34 +-
>   15 files changed, 1160 insertions(+), 320 deletions(-)
> 

I'm running into an internal error after this series when running 
gdb.fortran/intrinsics.exp on 32-bit arm Ubuntu 18.04.

We're failing this particular assertion in eval_op_f_cmplx:

gdb_assert (kind_arg->code () == TYPE_CODE_COMPLEX);


kind_arg->code () == TYPE_CODE_ERROR. I see gdb/f-lang.c initializing 
some types to TYPE_CODE_ERROR if they're not supported. Should we fail 
gracefully in this particular case?

  parent reply	other threads:[~2022-04-25 12:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  8:18 Nils-Christian Kempke
2022-04-11  8:18 ` [PATCH v3 11/11] gdb/doc: add section about Fortran intrinsic functions and types Nils-Christian Kempke
2022-04-11 11:38   ` Eli Zaretskii
2022-04-11 12:08     ` Kempke, Nils-Christian
2022-04-25 12:52 ` Luis Machado [this message]
2022-04-25 13:19   ` [PATCH v3 00/11] Improve Fortran intrinsic types and procedures Kempke, Nils-Christian
2022-04-25 13:21     ` Kempke, Nils-Christian
2022-04-25 13:41     ` Luis Machado

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=b262a336-02cc-a555-3857-00e55e4e2026@arm.com \
    --to=luis.machado@arm.com \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).