public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amylaar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29963] could speed up variable access with different object layout
Date: Thu, 01 Nov 2012 21:42:00 -0000	[thread overview]
Message-ID: <bug-29963-4-MQ4HP8WY2L@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29963-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29963

--- Comment #2 from Jorn Wolfgang Rennecke <amylaar at gcc dot gnu.org> 2012-11-01 21:42:12 UTC ---
(In reply to comment #1)
> I'm not sure how the proposed optimization could be done in a generic way.  It
> would not work for code (i.e. text section) that resides in read-only memory,
> such as ROM or MMU read-only pages.

In that case, you could indeed only do this optimization for constant
variables / arrays.

But it is not uncommon to load the program into RAM before executing,
e.g. because the ROM it's stored in is too slow.  In this case, placing
the program code in a writable segment is merely a matter of policy;
the user would be expected have control if this optimization is enabled,
taking into account if there are any overriding security concerns.


  parent reply	other threads:[~2012-11-01 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-29963-4@http.gcc.gnu.org/bugzilla/>
2012-11-01 21:27 ` olegendo at gcc dot gnu.org
2012-11-01 21:42 ` amylaar at gcc dot gnu.org [this message]
2012-11-13  0:54 ` olegendo at gcc dot gnu.org

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-29963-4-MQ4HP8WY2L@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).