public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Fangrui Song <maskray@google.com>
To: gcc-patches@gcc.gnu.org, Florian Weimer <fweimer@redhat.com>,
	 "H.J. Lu" <hjl.tools@gmail.com>, Jan Beulich <jbeulich@suse.com>,
	Jan Hubicka <hubicka@ucw.cz>,  Michael Matz <matz@suse.de>,
	Uros Bizjak <ubizjak@gmail.com>
Subject: Re: [PATCH v4] i386: Allow -mlarge-data-threshold with -mcmodel=large
Date: Wed, 27 Sep 2023 10:54:26 -0700	[thread overview]
Message-ID: <CAFP8O3L03NG2iM-FTLD1ORL1ryJtx+2hSnTb5hTSRdo9_F9hMw@mail.gmail.com> (raw)
In-Reply-To: <CAFP8O3KTS94OvV0meuES4zifyAXYbVejitUfHAcKDw1OHmF21Q@mail.gmail.com>

On Wed, Sep 13, 2023 at 11:19 AM Fangrui Song <maskray@google.com> wrote:
>
> On Tue, Aug 22, 2023 at 12:19 AM Fangrui Song <maskray@google.com> wrote:
> >
> > On Tue, Aug 1, 2023 at 12:51 PM Fangrui Song <maskray@google.com> wrote:
> > >
> > > When using -mcmodel=medium, large data objects larger than the
> > > -mlarge-data-threshold threshold are placed into large data sections
> > > (.lrodata, .ldata, .lbss and some variants).  GNU ld and ld.lld 17 place
> > > .l* sections into separate output sections.  If small and medium code
> > > model object files are mixed, the .l* sections won't exert relocation
> > > overflow pressure on sections in object files built with -mcmodel=small.
> > >
> > > However, when using -mcmodel=large, -mlarge-data-threshold doesn't
> > > apply.  This means that the .rodata/.data/.bss sections may exert
> > > relocation overflow pressure on sections in -mcmodel=small object files.
> > >
> > > This patch allows -mcmodel=large to generate .l* sections and drops an
> > > unneeded documentation restriction that the value must be the same.
> > >
> > > Link: https://groups.google.com/g/x86-64-abi/c/jnQdJeabxiU
> > > ("Large data sections for the large code model")
> > >
> > > Signed-off-by: Fangrui Song <maskray@google.com>
> > >
> > > ---
> > > Changes from v1 (https://gcc.gnu.org/pipermail/gcc-patches/2023-April/616947.html):
> > > * Clarify commit message. Add link to https://groups.google.com/g/x86-64-abi/c/jnQdJeabxiU
> > >
> > > Changes from v2
> > > * Drop an uneeded limitation in the documentation.
> > >
> > > Changes from v3
> > > * Change scan-assembler directives to use \. to match literal .
> > > ---
> > >  gcc/config/i386/i386.cc                    | 15 +++++++++------
> > >  gcc/config/i386/i386.opt                   |  2 +-
> > >  gcc/doc/invoke.texi                        |  6 +++---
> > >  gcc/testsuite/gcc.target/i386/large-data.c | 13 +++++++++++++
> > >  4 files changed, 26 insertions(+), 10 deletions(-)
> > >  create mode 100644 gcc/testsuite/gcc.target/i386/large-data.c
> > >
> > > [...]
> >
> > Ping:)
>
> Ping:) https://gcc.gnu.org/pipermail/gcc-patches/2023-August/625993.html
>
> (I don't have write access to gcc.)
>
>
> --
> 宋方睿

Ping? :) https://gcc.gnu.org/pipermail/gcc-patches/2023-August/625993.html

(I don't have write access to gcc.)


-- 
宋方睿

  reply	other threads:[~2023-09-27 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 19:51 Fangrui Song
2023-08-22  7:19 ` Fangrui Song
2023-09-13 18:19   ` Fangrui Song
2023-09-27 17:54     ` Fangrui Song [this message]
2023-10-16 17:12 ` Uros Bizjak
2023-10-16 18:24   ` [PATCH v5] " Fangrui Song
2023-10-16 19:10     ` Uros Bizjak
2023-10-16 19:58       ` Fangrui Song
2023-10-16 21:46         ` Uros Bizjak

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=CAFP8O3L03NG2iM-FTLD1ORL1ryJtx+2hSnTb5hTSRdo9_F9hMw@mail.gmail.com \
    --to=maskray@google.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=hubicka@ucw.cz \
    --cc=jbeulich@suse.com \
    --cc=matz@suse.de \
    --cc=ubizjak@gmail.com \
    /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).