From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8766] Compiling host-gcc-final-4.9.3 broken on i386
Date: Sun, 06 Mar 2016 13:27:31 +0000 [thread overview]
Message-ID: <bug-8766-163-Fm8qtlzXbf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8766-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=8766
--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
After some research, it seems to be an x86 specific issue. The file causing
problems is libgcc/generic-morestack-thread.c, which gets included in the build
by libgcc/config/t-stack. It is related to the implementation of -fsplit-stack,
which is only supported on x86 32/64.
So on other architectures, a no thread configuration should still build fine.
However, seeing that on a major arch like x86 the nothread support has been
broken for a while (-fsplit-stack has been around since gcc 4.6) really makes
me wonder if we should continue to support the no thread solution.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2016-03-06 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 11:08 [Buildroot] [Bug 8766] New: Compiling host-gcc-final-4.9.3 broken on i386 bugzilla at busybox.net
2016-03-06 12:51 ` [Buildroot] [Bug 8766] " bugzilla at busybox.net
2016-03-06 12:55 ` bugzilla at busybox.net
2016-03-06 13:27 ` bugzilla at busybox.net [this message]
2016-03-08 21:07 ` bugzilla at busybox.net
2016-04-19 21:26 ` bugzilla at busybox.net
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=bug-8766-163-Fm8qtlzXbf@https.bugs.busybox.net/ \
--to=bugzilla@busybox.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 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.