From: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
To: Tom Tromey <tom@tromey.com>,
Nils-Christian Kempke via Gdb-patches
<gdb-patches@sourceware.org>
Subject: RE: [PATCH 09/11] gdb/fortran: rewrite intrinsic handling and add some missing overloads
Date: Fri, 8 Apr 2022 12:49:59 +0000 [thread overview]
Message-ID: <CY4PR1101MB20715BC8B285D890FB0150A7B8E99@CY4PR1101MB2071.namprd11.prod.outlook.com> (raw)
In-Reply-To: <87bkxdaqz3.fsf@tromey.com>
> From: Tom Tromey <tom@tromey.com>
> Sent: Thursday, April 7, 2022 4:49 PM
> Thanks for the patch.
> I found one minor problem in this one. You don't have to resubmit after
> fixing it, though.
>
> > After adding more overloads to the intrinsics handling, some of the
> > operation names were no longer accurate. E.g. UNOP_FORTRAN_CEILING
> > has been renamed to FORTRAN_CEILING as it is no longer a purely unary
> > intrinsic function.
>
> Eventually I'd like to get rid of this operator enum entirely, but it's
> also fine to make the names more correct in the meantime.
Thanks for the review!
I also thought about this while doing the changes.. But I did not want the series
to become even more invasive. Should I touch the Fortran intrinsics handling
in the new future again I'll do that, too (probably while checking the intrinsics code
test coverage..).
>
> > + case FORTRAN_LBOUND:
> > + case FORTRAN_UBOUND:
> > + pstate->push_new<fortran_bound_2arg>
> > + (code, pstate->pop (), pstate->pop ());
>
> I don't think you can rely on the order of evaluation here. (C++ did
> change this, but after C++11, I think.) Instead you need to introduce
> temporaries to control the ordering.
>
Good spot, thanks!
I'll resubmit patch [PATCH 11/11] only then.
Cheers, Nils
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-04-08 12:50 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 [this message]
2022-04-13 5:14 ` Tom de Vries
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=CY4PR1101MB20715BC8B285D890FB0150A7B8E99@CY4PR1101MB2071.namprd11.prod.outlook.com \
--to=nils-christian.kempke@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).