From: Joern Rennecke <amylaar@redhat.com>
To: rth@redhat.com (Richard Henderson)
Cc: jh@suse.cz (Jan Hubicka),
gcc-patches@gcc.gnu.org, patches@x86-64.org, gcc@gcc.gnu.org
Subject: Re: RFC: BB duplication code
Date: Wed, 22 Aug 2001 16:04:00 -0000 [thread overview]
Message-ID: <200108222304.f7MN4mR04140@phal.cambridge.redhat.com> (raw)
In-Reply-To: <20010822121440.H29601@redhat.com>
> In the case of JUMP_TABLES_IN_TEXT_SECTION, yes, you absolutely cannot
> share the table. This is used by targets that use pc-relative addressing
> from the jump instruction to the table. VAX is the most extreme example
> in that the entire table is an argument to the instruction.
This is target-dependent. Some targets just put the jump table in the text
section because the linker can't handle cross-section differences, and
they use differences (either always or for pic / PIC).
next prev parent reply other threads:[~2001-08-22 16:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 11:29 Jan Hubicka
2001-08-22 12:14 ` Richard Henderson
2001-08-22 12:27 ` Jan Hubicka
2001-08-22 13:04 ` Richard Henderson
2001-08-23 6:44 ` Jan Hubicka
2001-08-23 16:19 ` Richard Henderson
2001-08-24 6:35 ` Jan Hubicka
2001-09-07 20:34 ` Loop optimiser upgrade (Was RFC: BB duplication code) Michael Hayes
2001-09-07 22:23 ` Daniel Berlin
2001-09-08 9:15 ` Jan Hubicka
2001-09-08 8:57 ` Jan Hubicka
2001-09-08 14:00 ` Daniel Berlin
2001-09-08 9:09 ` Jan Hubicka
2001-09-08 16:56 ` Michael Hayes
2001-09-09 1:23 ` Jan Hubicka
2001-09-26 17:27 ` Jan Hubicka
2001-09-08 9:33 ` Jan Hubicka
2001-09-19 22:23 ` Joern Rennecke
2001-09-21 19:11 ` Michael Hayes
2001-09-21 21:16 ` Joern Rennecke
2001-09-23 4:29 ` Michael Hayes
2001-09-24 4:34 ` Jan Hubicka
2001-09-22 10:17 ` Jan Hubicka
2001-08-22 16:04 ` Joern Rennecke [this message]
2001-08-22 16:44 ` RFC: BB duplication code Richard Henderson
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=200108222304.f7MN4mR04140@phal.cambridge.redhat.com \
--to=amylaar@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=patches@x86-64.org \
--cc=rth@redhat.com \
/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).