public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: John David Anglin <dave@hiauly1.hia.nrc.ca>
To: binutils@sourceware.org
Subject: [committed] Align data segments to maxpagesize on hppa-linux
Date: Fri, 18 Feb 2011 18:29:00 -0000	[thread overview]
Message-ID: <20110218182854.GA15444@hiauly1.hia.nrc.ca> (raw)

The PA-RISC architecture utilizes VIPT caches.  Some implementations
do not support nonequivalent aliases even for readonly mappings.

The following change aligns the data segment to a maxpagesize
boundary.  This forces the file offset for the data segment to be
maxpagsize aligned.  This avoids nonequivalent mappings for the
boundary between the text and data segments.

Committed to head.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

2011-02-18  John David Anglin  <dave.anglin@nrc-cnnrc.gc.ca>

	PR ld/12376
	emulparams/hppalinux.sh (DATA_ADDR): Define.
	(SHLIB_DATA_ADDR): Likewise.

Index: emulparams/hppalinux.sh
===================================================================
RCS file: /cvs/src/src/ld/emulparams/hppalinux.sh,v
retrieving revision 1.14
diff -u -3 -p -r1.14 hppalinux.sh
--- emulparams/hppalinux.sh	22 Oct 2008 05:20:44 -0000	1.14
+++ emulparams/hppalinux.sh	15 Feb 2011 14:30:24 -0000
@@ -8,6 +8,8 @@ NO_REL_RELOCS=yes
 TEXT_START_ADDR=0x10000
 TARGET_PAGE_SIZE=0x10000
 MAXPAGESIZE="CONSTANT (MAXPAGESIZE)"
+DATA_ADDR="ALIGN(${MAXPAGESIZE})"
+SHLIB_DATA_ADDR="ALIGN(${MAXPAGESIZE})"
 ARCH=hppa
 MACHINE=hppa1.1    # We use 1.1 specific features.
 NOP=0x08000240

                 reply	other threads:[~2011-02-18 18:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110218182854.GA15444@hiauly1.hia.nrc.ca \
    --to=dave@hiauly1.hia.nrc.ca \
    --cc=binutils@sourceware.org \
    --cc=dave.anglin@nrc-cnrc.gc.ca \
    /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).