From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] xtensa: toolchain fix for compiling huge functions
Date: Tue, 18 Aug 2015 23:29:17 +0200 [thread overview]
Message-ID: <20150818212917.GG3799@free.fr> (raw)
In-Reply-To: <1439418003-23805-1-git-send-email-jcmvbkbc@gmail.com>
Max, All,
On 2015-08-13 01:19 +0300, Max Filippov spake thusly:
> this series backports binutils and gcc patches that add auto-litpools option
> and replaces text-section-literals ABI flag for xtensa with auto-litpools.
> With that change compiling huge functions should no longer be an issue on
> xtensa. Obviously that change will break builds with pre-built toolchain.
I'm not a huge fan of this series.
- First, they are "feature patches" (even if backported) to critical
components (gcc, binutils).
- Then, patches 3 and 4 will break external toolchains.
- Finally, it seems to me quite some efforst for "just" one package.
So, I'd say we wait for gcc + binutils to spew out releases with those
changes, then we can incorporate those versions in Buildroot, and make
OpenCV depend on _GCC_AT_LEAST_X_Y ...
Note: those comments are also valid for the unwind patch you sent
later...
Note-2: I know this might be a very difficult job you've made,
backporting those fixes. Still, I don;t think they are fit for having
in Buldroot.
Regards,
Yann E. MORIN.
> Max Filippov (4):
> binutils: backport auto-litpools xtensa gas option
> gcc: backport mauto-litpools xtensa option
> xtensa: switch from text-section-literals to auto-litpools
> Revert "opencv: mark as not available on Xtensa"
>
> package/Makefile.in | 4 +-
> .../2.24/913-xtensa-add-auto-litpools-option.patch | 698 ++++++++++++++++++++
> .../913-xtensa-add-auto-litpools-option.patch | 699 +++++++++++++++++++++
> .../870-xtensa-add-mauto-litpools-option.patch | 290 +++++++++
> .../870-xtensa-add-mauto-litpools-option.patch | 290 +++++++++
> .../870-xtensa-add-mauto-litpools-option.patch | 290 +++++++++
> package/gcc/gcc.mk | 6 +-
> package/opencv/Config.in | 3 -
> 8 files changed, 2272 insertions(+), 8 deletions(-)
> create mode 100644 package/binutils/2.24/913-xtensa-add-auto-litpools-option.patch
> create mode 100644 package/binutils/2.25.1/913-xtensa-add-auto-litpools-option.patch
> create mode 100644 package/gcc/4.8.5/870-xtensa-add-mauto-litpools-option.patch
> create mode 100644 package/gcc/4.9.3/870-xtensa-add-mauto-litpools-option.patch
> create mode 100644 package/gcc/5.2.0/870-xtensa-add-mauto-litpools-option.patch
>
> --
> 1.8.1.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-08-18 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 22:19 [Buildroot] [PATCH 0/4] xtensa: toolchain fix for compiling huge functions Max Filippov
2015-08-12 22:20 ` [Buildroot] [PATCH 1/4] binutils: backport auto-litpools xtensa gas option Max Filippov
2015-08-12 22:20 ` [Buildroot] [PATCH 2/4] gcc: backport mauto-litpools xtensa option Max Filippov
2015-08-12 22:20 ` [Buildroot] [PATCH 3/4] xtensa: switch from text-section-literals to auto-litpools Max Filippov
2015-08-12 22:20 ` [Buildroot] [PATCH 4/4] Revert "opencv: mark as not available on Xtensa" Max Filippov
2015-08-18 21:29 ` Yann E. MORIN [this message]
2015-08-18 22:20 ` [Buildroot] [PATCH 0/4] xtensa: toolchain fix for compiling huge functions Max Filippov
2015-10-04 16:28 ` Thomas Petazzoni
2015-10-05 14:52 ` Max Filippov
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=20150818212917.GG3799@free.fr \
--to=yann.morin.1998@free.fr \
--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