From: Chris Zankel <chris@zankel.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] xtensa: add config option to enable longcalls option
Date: Tue, 04 Dec 2012 12:40:51 -0800 [thread overview]
Message-ID: <50BE5FD3.4000502@zankel.net> (raw)
In-Reply-To: <87wqwxmv7t.fsf@dell.be.48ers.dk>
Hi,
On 12/04/2012 12:13 PM, Peter Korsgaard wrote:
>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Hi,
>
> >> 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.
>
> Thomas> I'd prefer to have it always enabled, I'd say. We try to not add
> Thomas> gazillions of very detailed architecture-specific options that are
> Thomas> hard to understand. Hardcore users will know how/where to remove this
> Thomas> option is they need, or they can even override it by passing a
> Thomas> -mno-longcalls option in BR2_TARGET_OPTIMIZATION.
>
> Thomas> What do you think?
>
> I agree. Lets use the safe option by default.
>
Not sure what you mean with the 'safe option'? I'm also not sure what
the preference for options is when you pass both, the -mlongcalls and
-mno-longcalls option at the same time?
Anyway, I'm fine with whatever solution you come up with, as long as it
makes it into the tree :-)
Thanks,
-Chris
next prev parent reply other threads:[~2012-12-04 20:40 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
2012-12-04 9:17 ` Thomas Petazzoni
2012-12-04 20:13 ` Peter Korsgaard
2012-12-04 20:40 ` Chris Zankel [this message]
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=50BE5FD3.4000502@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