From: Tom de Vries <tdevries@suse.de>
To: Nils-Christian Kempke <nils-christian.kempke@intel.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH 09/11] gdb/fortran: rewrite intrinsic handling and add some missing overloads
Date: Wed, 13 Apr 2022 07:14:33 +0200 [thread overview]
Message-ID: <db1bc56e-8d63-2618-1ffc-291cd635096b@suse.de> (raw)
In-Reply-To: <20220309103922.3257803-10-nils-christian.kempke@intel.com>
On 3/9/22 11:39, Nils-Christian Kempke via Gdb-patches wrote:
> * gdb.fortran/lbound-ubound.F90: Add arrays with possibly
> overflowing dimensions and add some test.
> * gdb.fortran/lbound-ubound.exp: Add LBOUND/UBOUND test for
> overflow in array dimensions when supplying the KIND parameter.
> * gdb.fortran/size.exp: Add tests for overflow when using the
> KIND parameter.
> * gdb.fortran/size.f90: Add compiled KIND parameter tests.
This caused some fails / regressions with target board unix/-m32, see:
- https://sourceware.org/bugzilla/show_bug.cgi?id=29053
PR29053 - [m32] FAIL: gdb.fortran/lbound-ubound.exp: test 12: check
value of lbound ('array_1d_4bytes_overflow') expression
- https://sourceware.org/bugzilla/show_bug.cgi?id=29054
PR29054 - [gdb/testsuite] Compilation failure of gdb.fortran/size.f90
with -m32
Thanks,
- Tom
next prev parent reply other threads:[~2022-04-13 5:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 10:39 [PATCH 00/11] Improve Fortran intrinsic types and procedures Nils-Christian Kempke
2022-03-09 10:39 ` [PATCH 01/11] gdb/f-lang: add Integer*1 to Fortran builtin types Nils-Christian Kempke
2022-04-07 14:28 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 02/11] gdb/f-lang: remove hidden ^L characters Nils-Christian Kempke
2022-04-07 14:28 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 03/11] gdb/fortran: fix complex type in Fortran builtin types Nils-Christian Kempke
2022-04-07 14:30 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 04/11] gdb/fortran: reformat build_fortran_types in f-lang.c Nils-Christian Kempke
2022-04-07 14:30 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 05/11] gdb/fortran: change default logical type to builtin_logical Nils-Christian Kempke
2022-04-07 14:32 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 06/11] gdb/fortran: clean-up Fortran intrinsic types Nils-Christian Kempke
2022-04-07 14:33 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 07/11] gdb/fortran: Change GDB print for fortran default types Nils-Christian Kempke
2022-04-07 14:37 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 08/11] gdb/fortran: rename f77_keywords to f_keywords Nils-Christian Kempke
2022-04-07 14:37 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 09/11] gdb/fortran: rewrite intrinsic handling and add some missing overloads Nils-Christian Kempke
2022-04-07 14:49 ` Tom Tromey
2022-04-08 12:49 ` Kempke, Nils-Christian
2022-04-13 5:14 ` Tom de Vries [this message]
2022-04-20 16:10 ` Kempke, Nils-Christian
2022-03-09 10:39 ` [PATCH 10/11] gdb/fortran/testsuite: add complex from integers test Nils-Christian Kempke
2022-04-07 14:49 ` Tom Tromey
2022-04-07 14:50 ` Tom Tromey
2022-03-09 10:39 ` [PATCH 11/11] gdb/doc: add section about fortran intrinsic functions and types Nils-Christian Kempke
2022-03-09 12:49 ` Eli Zaretskii
2022-03-09 17:01 ` 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=db1bc56e-8d63-2618-1ffc-291cd635096b@suse.de \
--to=tdevries@suse.de \
--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).