From: Richard Biener <richard.guenther@gmail.com>
To: Roger Sayle <roger@nextmovesoftware.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Some PINGs
Date: Mon, 8 Nov 2021 09:50:42 +0100 [thread overview]
Message-ID: <CAFiYyc3JoZKd65R_oXfD07ffuEqWb3-JoFkQtueJ-1F_e+tC6g@mail.gmail.com> (raw)
In-Reply-To: <016901d7d35c$8d2b0de0$a78129a0$@nextmovesoftware.com>
On Sat, Nov 6, 2021 at 11:21 PM Roger Sayle <roger@nextmovesoftware.com> wrote:
>
>
> I wonder if reviewers could take a look (or a second look) at some of my
> outstanding patches.
>
> Four nvptx backend patches:
>
> nvptx: Use cvt to perform sign-extension of truncation.
> https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578256.html
>
> nvptx: Add (experimental) support for HFmode with -misa=sm_53
> https://gcc.gnu.org/pipermail/gcc-patches/2021-September/579623.html
>
> nvptx: Adds uses of -misa=sm_75 and -misa=sm_80
> https://gcc.gnu.org/pipermail/gcc-patches/2021-September/579691.html
>
> Transition nvptx backend to STORE_FLAG_VALUE = 1
> https://gcc.gnu.org/pipermail/gcc-patches/2021-October/581004.html
>
> Two middle-end patches:
>
> Simplify paradoxical subreg extensions of TRUNCATE
> https://gcc.gnu.org/pipermail/gcc-patches/2021-September/578848.html
>
> PR middle-end/100810: Penalize IV candidates with undefined value bases
> https://gcc.gnu.org/pipermail/gcc-patches/2021-August/578441.html
I did comment on this one, noting the more general issue. My opinion is still
that doing heavy lifting in IVOPTs is misplaced.
> And a gfortran patch:
>
> gfortran: Improve translation of POPPAR intrinsic
> https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548055.html
>
>
> Many thanks in advance,
> Roger
> --
>
>
next prev parent reply other threads:[~2021-11-08 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 22:20 Roger Sayle
2021-11-07 0:36 ` Jeff Law
2021-11-07 14:07 ` Roger Sayle
2021-11-08 8:50 ` Richard Biener [this message]
2021-11-08 14:02 ` Roger Sayle
2021-11-08 15:40 ` Richard Biener
2021-11-09 9:18 ` Richard Biener
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=CAFiYyc3JoZKd65R_oXfD07ffuEqWb3-JoFkQtueJ-1F_e+tC6g@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.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).