public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yang Yujie <yangyujie@loongson.cn>
To: gcc-patches@gcc.gnu.org
Cc: chenglulu@loongson.cn, xuchenghua@loongson.cn,
	 Yang Yujie <yangyujie@loongson.cn>
Subject: Re: [PATCH v4] LoongArch: Split loongarch_option_override_internal into smaller procedures
Date: Sat, 30 Mar 2024 16:45:15 +0800	[thread overview]
Message-ID: <fu3l3o2sqypjpipin6p53jwlftkdm4nsuynjeshlxkrbasbghs@kmokoluaecxb> (raw)
In-Reply-To: <20240330084313.827920-2-yangyujie@loongson.cn>

v1 -> v2:
- Rebased to master.
- Specifies "(void)" for the empty parameter list of loongarch_global_init.

v2 -> v3:
- Keep the original option-processing behavior (-march=la664 enables -mrecip=all)
  and fix the ICE when -mfrecipe is not passed with -mrecip.

v3 -> v4:
- Rewrite changelog.


  reply	other threads:[~2024-03-30  9:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30  8:43 Yang Yujie
2024-03-30  8:45 ` Yang Yujie [this message]
2024-04-01  1:17 ` [pushed][PATCH " chenglulu

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=fu3l3o2sqypjpipin6p53jwlftkdm4nsuynjeshlxkrbasbghs@kmokoluaecxb \
    --to=yangyujie@loongson.cn \
    --cc=chenglulu@loongson.cn \
    --cc=gcc-patches@gcc.gnu.org \
    --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).