public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lulu Cheng <chenglulu@loongson.cn>
To: Hans-Peter Nilsson <hp@bitrange.com>, Xi Ruoyao <xry111@xry111.site>
Cc: gcc-patches@gcc.gnu.org, Youling Tang <tangyouling@loongson.cn>,
	Chenghua Xu <xuchenghua@loongson.cn>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jinyang He <hejinyang@loongson.cn>, Wang Xuerui <i@xen0n.name>
Subject: Re: [PATCH v6] LoongArch: add addr_global attribute
Date: Thu, 18 Aug 2022 11:54:26 +0800	[thread overview]
Message-ID: <9d449d35-529b-a883-dce1-f1f441718000@loongson.cn> (raw)
In-Reply-To: <alpine.BSF.2.20.16.2208172255240.38381@arjuna.pair.com>


在 2022/8/18 上午10:56, Hans-Peter Nilsson 写道:
> On Mon, 15 Aug 2022, Xi Ruoyao via Gcc-patches wrote:
>
>> Can we make a final solution to this soon?  Now the merge window of
>> Linux 6.0 is closed and we have two Linux kernel releases not possible
>> to be built with Binutils or GCC with new relocation types.  This is
>> just ugly...
>>
>> On Fri, 2022-08-12 at 17:17 +0800, Xi Ruoyao via Gcc-patches wrote:
>>> v5 -> v6:
>>>
>>> * still use "addr_global" as we don't have a better name.
> "far"?
>
> brgds, H-P

Sorry, I have already added the code of cmodel=extreme, and I am sorting 
out the code and test cases. I still insist on using 
__attribute__(model(extreme)) to describe the variables of precpu. I 
will send my patch today.


  reply	other threads:[~2022-08-18  3:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12  9:17 Xi Ruoyao
2022-08-15 11:26 ` Xi Ruoyao
2022-08-18  2:56   ` Hans-Peter Nilsson
2022-08-18  3:54     ` Lulu Cheng [this message]
2022-08-18  4:27       ` Xi Ruoyao

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=9d449d35-529b-a883-dce1-f1f441718000@loongson.cn \
    --to=chenglulu@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hejinyang@loongson.cn \
    --cc=hp@bitrange.com \
    --cc=i@xen0n.name \
    --cc=tangyouling@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).