public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Thomas Koenig <tkoenig@netcologne.de>,
	 Jan Hubicka <hubicka@ucw.cz>,
	 "fortran\@gcc.gnu.org" <fortran@gcc.gnu.org>,
	 gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] Fix PR 84487, large rodata increase in tonto and other programs
Date: Mon, 15 Apr 2019 11:55:00 -0000	[thread overview]
Message-ID: <87lg0b4h7g.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAFiYyc3B2_=SHgteQrC=u3sCvQ+zhs-YJzVPrXo+5iffpoiJOA@mail.gmail.com>	(Richard Biener's message of "Mon, 15 Apr 2019 09:11:09 +0200")

* Richard Biener:

> Of course adding sth like a .robss section would be nice.

I think this is strictly a link editor issue because a read-only PT_LOAD
directive with a memory size larger than the file size already produces
read-only zero pages, without requiring a file allocation.

Thanks,
Florian

  parent reply	other threads:[~2019-04-15 11:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-13 19:36 Thomas Koenig
2019-04-14  9:51 ` Paul Richard Thomas
2019-04-15  7:26 ` Richard Biener
2019-04-15 11:54   ` Jan Hubicka
2019-04-15 11:55   ` Florian Weimer [this message]
2019-04-15 20:08     ` Segher Boessenkool
2019-04-16 10:06       ` Florian Weimer
2019-04-16 10:12         ` Richard Biener
2019-04-16 10:20           ` Segher Boessenkool
2019-04-16 10:16         ` Segher Boessenkool
2019-04-16 10:17         ` Jakub Jelinek
2019-04-16 10:30           ` Segher Boessenkool
2019-04-17  7:35           ` Thomas König
2019-04-17  8:48             ` Richard Biener
2019-04-17 11:09               ` Florian Weimer
2019-04-17 12:23                 ` Andreas Schwab
2019-04-17 12:45                   ` Florian Weimer
2019-04-17 12:55                     ` Andreas Schwab
2019-04-17 13:13                       ` Florian Weimer

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=87lg0b4h7g.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=richard.guenther@gmail.com \
    --cc=tkoenig@netcologne.de \
    /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).