From: Jeffrey A Law <law@cygnus.com>
To: Bernd Schmidt <crux@pool.informatik.rwth-aachen.de>
Cc: egcs@cygnus.com, wilson@cygnus.com
Subject: Re: JUMP_TABLES_IN_TEXT_SECTION
Date: Sat, 04 Apr 1998 14:20:00 -0000 [thread overview]
Message-ID: <6791.891589844@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.SOL.3.90.980220112632.20928E-100000@clouseau.informatik.rwth-aachen.de>
In message <Pine.SOL.3.90.980220112632.20928E-100000@clouseau.informatik.rwth
-aachen.de>you write:
> The optimization manuals for Intel and AMD CPUs advise to put jump tables
> into the data section. To implement this, I've changed
> JUMP_TABLES_IN_TEXT_SECTION to have a value. For ix86-linux, the patch
> sets it to (flag_pic), which is probably appropriate for ix86-*bsd as well.
> I didn't change it, since I can't test those configurations.
> The MIPS port may also be worth looking at, it appears to kludge around the
> fact that the macro did not have a value until now.
>
> Bernd
>
> * final.c: Define JUMP_TABLES_IN_TEXT_SECTION to a default value
> of 0 if it isn't defined.
> (get_attr_length, shorten_branches, final_scan_insn): Test value
> of JUMP_TABLES_IN_TEXT_SECTION instead of just testing whether it
> is defined.
>
> * arc/arc.h: Define JUMP_TABLES_IN_TEXT_SECTION to 0.
> * m32r/m32r.h: Likewise.
> * rs6000/sysv4.h: Likewise.
> * arm/coff.h: Define JUMP_TABLES_IN_TEXT_SECTION to 1.
> * i386/386bsd.h: Likewise.
> * i386/freebsd-elf.h: Likewise.
> * i386/freebsd.h: Likewise.
> * i386/netbsd.h: Likewise.
> * i386/ptx4-i.h: Likewise.
> * i386/sysv4.h: Likewise.
> * pa/pa.h: Likewise.
> * rs6000/linux.h: Likewise.
> * rs6000/rs6000.h: Likewise.
> * sh/sh.h: Likewise.
> * sparc/sp64-elf.h: Likewise.
> * v850/v850.h: Likewise.
> * i386/linux.h: Define JUMP_TABLES_IN_TEXT_SECTION to (flag_pic).
The code in shorten_branches went through a major revision about a
week after you sent this patch. As a result the patch needs to be
revised to work with the new shorten_branches code.
If you make that update and resend the patch, I'll install it.
Thanks,
jeff
next prev parent reply other threads:[~1998-04-04 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-20 12:26 JUMP_TABLES_IN_TEXT_SECTION Bernd Schmidt
1998-04-04 14:20 ` Jeffrey A Law [this message]
1998-04-06 15:25 ` JUMP_TABLES_IN_TEXT_SECTION Bernd Schmidt
1998-04-06 17:35 ` JUMP_TABLES_IN_TEXT_SECTION Joern Rennecke
1998-04-07 19:34 ` JUMP_TABLES_IN_TEXT_SECTION Jeffrey A Law
1998-04-09 5:08 ` JUMP_TABLES_IN_TEXT_SECTION Bernd Schmidt
1998-05-22 0:32 ` JUMP_TABLES_IN_TEXT_SECTION Jeffrey A Law
1998-04-06 17:35 ` JUMP_TABLES_IN_TEXT_SECTION David Edelsohn
1998-04-08 4:34 ` JUMP_TABLES_IN_TEXT_SECTION Bernd Schmidt
1998-04-07 6:54 ` JUMP_TABLES_IN_TEXT_SECTION John Carr
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=6791.891589844@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=crux@pool.informatik.rwth-aachen.de \
--cc=egcs@cygnus.com \
--cc=wilson@cygnus.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).