public inbox for
 help / color / mirror / Atom feed
From: Xi Ruoyao <>
To: Lulu Cheng <>,
Subject: Re: [PATCH v3] LoongArch: Optimize immediate load.
Date: Fri, 04 Nov 2022 10:22:57 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 2022-11-01 at 20:04 +0800, Lulu Cheng wrote:
> gcc/ChangeLog:
>         * config/loongarch/ (x): New constraint.
>         * config/loongarch/ (struct loongarch_address_info):
>         Adds a method to load the immediate 32 to 64 bit field.
>         (struct loongarch_integer_op): Define a new member curr_value,
>         that records the value of the number stored in the destination
>         register immediately after the current instruction has run.
>         (LARCH_MAX_INTEGER_OPS): Define this macro as 3.
>         (LU32I_B): Move to the loongarch.h.
>         (LU52I_B): Likewise.
>         (loongarch_build_integer): Adds a method to load the immediate
>         32 to 63 bits.
>         (loongarch_move_integer): Likewise.

We need to mention "call set_unique_reg_note" here because it seems the
key to resolve the issue.

Otherwise LGTM.

>         (loongarch_print_operand_reloc): Modifying comment information.
>         * config/loongarch/loongarch.h (LU32I_B): Move from
>         (LU52I_B): Likewise.
>         (HWIT_UC_0xFFFFFFFF): New macro.
>         (HI32_OPERAND): New macro.
>         * config/loongarch/ (load_hi32): New template.
>         * config/loongarch/ (const_hi32_operand): Determines
>         whether the value is an immediate number that has a value of only
>         the higher 32 bits.
>         (hi32_mask_operand): Immediately counts the mask of 32 to 61 bits.

Xi Ruoyao <>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2022-11-04  2:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 12:04 Lulu Cheng
2022-11-04  2:22 ` Xi Ruoyao [this message]
2022-11-04  2:33   ` Lulu Cheng
2022-11-04  2:56     ` Xi Ruoyao
2022-11-04  3:07       ` Lulu Cheng

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).