From: Thomas Koenig <tkoenig@netcologne.de>
To: Harald Anlauf <anlauf@gmx.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: *Ping*: [PATCH] PR fortran/96711 - ICE on NINT() Function
Date: Mon, 7 Sep 2020 07:09:25 +0200 [thread overview]
Message-ID: <3e6df45e-6270-d6eb-dcf0-0dee57158d66@netcologne.de> (raw)
In-Reply-To: <trinity-1c132f66-19e7-4cc6-a568-6d5b6823bc4f-1599158544006@3c-app-gmx-bs44>
Hi Harald,
> *ping*
I don't really know about the convert vs. fold_convert issue either,
but if it works, it works.
Regarding the patch: Could you change the test caes into a
run-time test and check for the results both for compile-time
simplification and evaluation at run-time? Just to make sure that
fold_convert wasn't trying to tell us something that convert doesn't...
OK with that change.
Thanks for the patch!
Best regards
Thomas
next prev parent reply other threads:[~2020-09-07 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 21:08 Harald Anlauf
2020-09-03 18:42 ` *Ping*: " Harald Anlauf
2020-09-07 5:09 ` Thomas Koenig [this message]
2020-09-07 19:46 ` Harald Anlauf
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=3e6df45e-6270-d6eb-dcf0-0dee57158d66@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.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).