public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: caiyinyu <caiyinyu@loongson.cn>,
	 adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
	 i.swmail@xen0n.name,  xuchenghua@loongson.cn
Subject: Re: [PATCH] LoongArch: Use medium cmodel build libc_nonshared.a.
Date: Wed, 30 Nov 2022 08:40:43 +0100	[thread overview]
Message-ID: <87sfi099fo.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <33054b9098f4ef690cd1639e96b2c148e9e9e490.camel@xry111.site> (Xi Ruoyao's message of "Wed, 23 Nov 2022 19:18:18 +0800")

* Xi Ruoyao:

> On Wed, 2022-11-23 at 11:31 +0100, Florian Weimer wrote:
>> But shouldn't the medium model be the GCC default if it is required for
>> building applications?
>
> Small code model can support a 128MiB .text section, and most
> applications have a .text section < 128MiB.  But Firefox libxul.so can
> be extremely large.
>
> It's not worthy to pay the cost everywhere just for satisfying a
> monster application.

I see, I wasn't aware that the limit was that large.

Thanks,
Florian


      parent reply	other threads:[~2022-11-30  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23  7:09 caiyinyu
2022-11-23  8:21 ` Xi Ruoyao
2022-11-23 10:31 ` Florian Weimer
2022-11-23 11:18   ` Xi Ruoyao
2022-11-30  6:55     ` 回复: " caiyinyu
     [not found]       ` <7ffa022e80ba4ab8942995da0d5c8371f180cb1b.camel@xry111.site>
2022-11-30  8:40         ` 回复: 回复: [PATCH] LoongArch: Use mediumcmodel " caiyinyu
2022-11-30  7:40     ` Florian Weimer [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=87sfi099fo.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=caiyinyu@loongson.cn \
    --cc=i.swmail@xen0n.name \
    --cc=libc-alpha@sourceware.org \
    --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).