From: czankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] xtensa: add config option to enable longcalls option
Date: Tue, 04 Dec 2012 00:36:32 -0800 [thread overview]
Message-ID: <50BDB610.7080304@zankel.net> (raw)
In-Reply-To: <20121203140912.1e09f0ea@skate>
On 12/3/12 5:09 AM, Thomas Petazzoni wrote:
> Dear Chris Zankel,
>
> On Mon, 3 Dec 2012 00:58:46 -0800, Chris Zankel wrote:
>> The longcalls option allows calls across a greater range of addresses.
>>
>> This option should be used when call targets can potentially be
>> out of range. It may degrade both code size and performance, but
>> the linker can generally optimize away the unnecessary overhead
>> when a call ends up within range.
>>
> Do we really want that as a configurable option? Isn't it possible
> instead to always generate longcalls, or to fix this on a per-package
> basis, when needed?
The actual distance between call and destination is probably very
dependent on compiler versions and compile options, etc., so might be
hard to figure out what packages are affected. We might end up with a
lot of packages with special Xtensa 'treatments'. Probably better to
just have it always there.
It should actually be fine to always compile with the longcalls option,
but I didn't just want to change it without having the option to keep
the old behavior, hence the option.
Thanks,
-Chris
next prev parent reply other threads:[~2012-12-04 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 8:58 [Buildroot] [PATCH v2] xtensa: add config option to enable longcalls option Chris Zankel
2012-12-03 13:09 ` Thomas Petazzoni
2012-12-04 8:36 ` czankel [this message]
2012-12-04 9:17 ` Thomas Petazzoni
2012-12-04 20:13 ` Peter Korsgaard
2012-12-04 20:40 ` Chris Zankel
2012-12-04 21:39 ` Thomas Petazzoni
2012-12-04 21:55 ` Peter Korsgaard
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=50BDB610.7080304@zankel.net \
--to=chris@zankel.net \
--cc=buildroot@busybox.net \
/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