public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95637] Read-only data assigned to `.sdata' rather than `.rodata'
Date: Mon, 15 Jun 2020 23:21:13 +0000	[thread overview]
Message-ID: <bug-95637-4-h0TH9VwE7Y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95637-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95637

--- Comment #3 from Jim Wilson <wilson at gcc dot gnu.org> ---
People have asked about constant pools before, but as far as I know no one has
tried to implement support for them yet.

We don't have a pc-relative load, so it would be a two instruction sequence
with auipc.  Unless maybe you load the base address into a register, which is
probably OK for rvi but may cause register pressure problems for rve.  We have
a 12-bit signed offset, +/-2K which limits the range we can address if you want
to put the base address in a register.  There could also complications with the
aggressive link time code relaxations that we do, depending on where you put
the constant pools and how you use them.  It isn't clear if constant pools are
better or worse than what we already have.

  parent reply	other threads:[~2020-06-15 23:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 11:15 [Bug target/95637] New: " macro@linux-mips.org
2020-06-11 21:06 ` [Bug target/95637] " wilson at gcc dot gnu.org
2020-06-12 21:37 ` macro@linux-mips.org
2020-06-15 23:21 ` wilson at gcc dot gnu.org [this message]
2020-06-23 22:58 ` macro@linux-mips.org
2020-06-28 10:40 ` ebotcazou at gcc dot gnu.org
2020-06-30  0:05 ` LpSolit at gmail dot com

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=bug-95637-4-h0TH9VwE7Y@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).