From: Joy Mukherjee <jmukherj@csgrad.cs.vt.edu>
To: <gcc-help@gcc.gnu.org>
Subject: Global addressing
Date: Tue, 04 Sep 2001 15:10:00 -0000 [thread overview]
Message-ID: <Pine.OSF.4.33.0109041809390.26258-100000@csgrad.cs.vt.edu> (raw)
In-Reply-To: <Pine.OSF.4.33.0109041751470.26258-100000@csgrad.cs.vt.edu>
Hi !
I need to relocate all the global variables of a program to some
other address and then force the executable to use the relocated set
instead of the original one . The problem is that when I looked at the
assembly code generated, it seems that the compiler uses direct addressing
for such globals .
Is there anyway I can force the compiler to use indexed addressing
ONLY for all variables - local/global ? I am working on the Intel-Linux
plateform . I would really appreciate any help .
Joy.
next parent reply other threads:[~2001-09-04 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.OSF.4.33.0109041751470.26258-100000@csgrad.cs.vt.edu>
2001-09-04 15:10 ` Joy Mukherjee [this message]
[not found] <oru1ybbtoo.fsf@free.redhat.lsd.ic.unicamp.br>
2001-09-10 14:28 ` Joy Mukherjee
2001-09-13 17:36 ` Alexandre Oliva
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=Pine.OSF.4.33.0109041809390.26258-100000@csgrad.cs.vt.edu \
--to=jmukherj@csgrad.cs.vt.edu \
--cc=gcc-help@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).