From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv4] bfin: fix issues with internal toolchain, re-enable C++ support
Date: Sat, 20 Aug 2016 00:27:38 +0200 [thread overview]
Message-ID: <20160819222738.GA22524@waldemar-brodkorb.de> (raw)
In-Reply-To: <1471638312-4799-1-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote,
> From: Waldemar Brodkorb <wbx@openadk.org>
>
> The three patches allow to compile applications using TLS emulation from
> libgcc or C++ applications.
>
> The patches 892-libgcc-mkmap-symver-support-skip_underscore.patch and
> 893-libgcc-config-bfin-use-the-generic-linker-version-in.patch fixes how
> libgcc is generated, by making the necessary libgcc symbols declared
> "GLOBAL", and therefore visible outside of libgcc. This fixes a large
> number of undefined reference issues (for either C++ applications or
> applications using TLS emulation). This was reported as gcc PR74748.
>
> The patch 894-libgcc-fix-DWARF-compilation-with-FDPIC-targets.patch
> allows to build DWARF in FDPIC mode. This patch replaces the older
> 892-disable-dwarf-bfin.patch, as instead of disabling DWARF support, it
> fixes it. This was reported as gcc PR68468.
>
> In order to get C++ working without unresolved symbols, we also need to
> disable symbol versioning (--disable-symvers). This is a remaining issue
> in gcc which will be investigated at a later point.
>
> Since this commit fixes C++ support in Blackfin, it re-enables the
> selection of C++ support for this architecture.
Tested and works great. Awesome. Wonderful.
Thanks for cleaning up my messy hacks :)
best regards
Waldemar
next prev parent reply other threads:[~2016-08-19 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 20:25 [Buildroot] [PATCHv4] bfin: fix issues with internal toolchain, re-enable C++ support Thomas Petazzoni
2016-08-19 22:27 ` Waldemar Brodkorb [this message]
2016-08-20 9:49 ` Thomas Petazzoni
2016-08-20 9:48 ` Thomas Petazzoni
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=20160819222738.GA22524@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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