From: Mikael Morin <morin-mikael@orange.fr>
To: Harald Anlauf <anlauf@gmx.de>, fortran <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR fortran/84784 - ICEs: verify_gimple failed with -fdefault-integer-8
Date: Thu, 27 Jan 2022 12:48:16 +0100 [thread overview]
Message-ID: <39f666ba-db26-dc71-af30-280052c53b4b@orange.fr> (raw)
In-Reply-To: <trinity-37d579c4-32f5-44e7-8eb9-9bdf422077f8-1643230795668@3c-app-gmx-bs37>
Le 26/01/2022 à 21:59, Harald Anlauf via Fortran a écrit :
> Dear Fortranners,
>
> the use of -fdefault-integer-8 exhibits several cases where
> we missed to convert the result of an intrinsic from the
> declared to the effective resulting type.
>
> The attached obvious patch fixes this for IMAGE_STATUS,
> TEAM_NUMBER, and POPCNT/POPPAR.
>
> OK for mainline if regtesting passes on x86_64-pc-linux-gnu?
>
This is not a regression, but should be safe.
Can you add a test of POPPAR, similar to that of POPCNT?
OK with that change.
prev parent reply other threads:[~2022-01-27 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 20:59 Harald Anlauf
2022-01-27 11:48 ` Mikael Morin [this message]
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=39f666ba-db26-dc71-af30-280052c53b4b@orange.fr \
--to=morin-mikael@orange.fr \
--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).