public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: chenglulu <chenglulu@loongson.cn>
To: Chenghui Pan <panchenghui@loongson.cn>, gcc-patches@gcc.gnu.org
Cc: xry111@xry111.site, i@xen0n.name, xuchenghua@loongson.cn
Subject: Re: [pushed][PATCH v2 0/3] LoongArch: Cleanup unused/redundant codes.
Date: Wed, 20 Mar 2024 10:29:48 +0800	[thread overview]
Message-ID: <9fe7e16c-eac7-18d1-20f2-85c95c425b4a@loongson.cn> (raw)
In-Reply-To: <20240315013027.183888-1-panchenghui@loongson.cn>

Pushed to r14-9562...r14-9564.

在 2024/3/15 上午9:30, Chenghui Pan 写道:
> Changes from v1: Some correction about ChangeLog format.
>
> There's some unused/redundant definitions inside LoongArch target support
> codes, these patches make a simple cleanup. Regression test passed.
>
> Chenghui Pan (3):
>    LoongArch: Remove unused/useless definitions.
>    LoongArch: Change loongarch_expand_vec_cmp()'s return type from bool
>      to void.
>    LoongArch: Combine UNITS_PER_FP_REG and UNITS_PER_FPREG macros.
>
>   gcc/config/loongarch/lasx.md            |  6 ++--
>   gcc/config/loongarch/loongarch-protos.h |  7 +----
>   gcc/config/loongarch/loongarch.cc       | 39 ++++---------------------
>   gcc/config/loongarch/loongarch.h        |  7 ++---
>   gcc/config/loongarch/lsx.md             |  6 ++--
>   5 files changed, 13 insertions(+), 52 deletions(-)
>


      parent reply	other threads:[~2024-03-20  2:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15  1:30 [PATCH " Chenghui Pan
2024-03-15  1:30 ` [PATCH v2 1/3] LoongArch: Remove unused/useless definitions Chenghui Pan
2024-03-15  1:30 ` [PATCH v2 2/3] LoongArch: Change loongarch_expand_vec_cmp()'s return type from bool to void Chenghui Pan
2024-03-15  1:30 ` [PATCH v2 3/3] LoongArch: Combine UNITS_PER_FP_REG and UNITS_PER_FPREG macros Chenghui Pan
2024-03-20  2:29 ` chenglulu [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=9fe7e16c-eac7-18d1-20f2-85c95c425b4a@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=i@xen0n.name \
    --cc=panchenghui@loongson.cn \
    --cc=xry111@xry111.site \
    --cc=xuchenghua@loongson.cn \
    /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).