From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: Building cross-toolchain for microblaze
Date: Fri, 04 Nov 2016 12:12:00 -0000 [thread overview]
Message-ID: <f5608edb-228f-da96-229e-381a387105b7@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1611040240470.20687@digraph.polyomino.org.uk>
On 04/11/2016 00:48, Joseph Myers wrote:
> Continuing the issues shown up by writing a script to build glibc for all
> ABIs, I find that MicroBlaze glibc does not build using the final compiler
> because MicroBlaze GCC always uses SJLJ exceptions (see
> gcc/common/config/microblaze/microblaze-common.c defining
> TARGET_EXCEPT_UNWIND_INFO to sjlj_except_unwind_info), which is not
> supported in glibc, resulting in undefined references to _Unwind_SjLj_*
> (glibc deliberately links with libgcc.a and *not* libgcc_eh.a and gets EH
> functionality via loading libgcc_s as needed, which is not implemented for
> the SJLJ case; in the static-only case there isn't a separate libgcc_eh so
> a build with the initial static-only compiler works accidentally).
>
> How is building MicroBlaze glibc meant to work? Is there some GCC patch
> missing upstream to use DWARF2 exceptions?
>
I could build a workable toolchain, at least for glibc building, by
configuring GCC with both '--disable-sjlj-exceptions' and
'--disable-shared'. I did not dig into the issue, but it was already
reported on maillist this same issue.
next prev parent reply other threads:[~2016-11-04 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 2:48 Joseph Myers
2016-11-04 12:12 ` Adhemerval Zanella [this message]
2016-11-04 13:08 ` Joseph Myers
2016-11-04 13:44 ` Adhemerval Zanella
2016-11-06 2:05 ` Waldemar Brodkorb
2016-11-07 15:46 ` Joseph Myers
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=f5608edb-228f-da96-229e-381a387105b7@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).