From: David Huggins-Daines <dhd@linuxcare.com>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: alan@linuxcare.com.au, parisc-linux@thepuffingroup.com,
parisc@lists.linuxcare.com
Subject: Re: Millicode calls, GP register, ld -r
Date: 12 Aug 2000 12:29:31 -0400 [thread overview]
Message-ID: <87itt6moic.fsf@linuxcare.com> (raw)
In-Reply-To: "John David Anglin"'s message of "Sat, 12 Aug 2000 12:07:56 -0400 (EDT)"
"John David Anglin" <dave@hiauly1.hia.nrc.ca> writes:
> The HP linker `-O' option eliminates unnecessary ADDIL instructions
Yes, currently our code generation is absolute crap, because we are
using ADDIL+LDO sequences for absolutely every DP or DLT
relative/indirect access.
Other BFD and GCC targets have optimizations to use 'short' data, bss,
got, and sometimes plt sections when possible. Long term I would
really like to implement this for hppa-linux.
I'm not at all sure how this is done though - can anyone point me to
some code or documentation that explains it?
--
dhd@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
next prev parent reply other threads:[~2000-08-12 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0008111413410.29780-100000@front.linuxcare.com.au>
2000-08-11 7:32 ` Millicode calls, GP register, ld -r Alan Modra
2000-08-11 12:30 ` Jeffrey A Law
2000-08-11 14:56 ` Matthew Wilcox
2000-08-11 16:43 ` John David Anglin
2000-08-11 20:23 ` David Huggins-Daines
2000-08-11 22:35 ` David Huggins-Daines
2000-08-12 0:17 ` Alan Modra
2000-08-12 1:35 ` Alan Modra
2000-08-12 15:23 ` David Huggins-Daines
2000-08-12 16:07 ` John David Anglin
2000-08-12 16:29 ` David Huggins-Daines [this message]
2000-08-12 18:13 ` Jeffrey A Law
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=87itt6moic.fsf@linuxcare.com \
--to=dhd@linuxcare.com \
--cc=alan@linuxcare.com.au \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@thepuffingroup.com \
--cc=parisc@lists.linuxcare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.