From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC][PATCH] bfin: fix two issues with internal toolchain
Date: Fri, 5 Aug 2016 22:43:42 +0200 [thread overview]
Message-ID: <20160805224342.1972c673@free-electrons.com> (raw)
In-Reply-To: <20160805195247.GA11252@waldemar-brodkorb.de>
Hello,
On Fri, 5 Aug 2016 21:52:47 +0200, Waldemar Brodkorb wrote:
> And libgcc_s.so.1 provides it:
> ./output/host/usr/bin/bfin-buildroot-linux-uclibc-nm
> ./output/host/usr/bfin-buildroot-linux-uclibc/sysroot/lib/libgcc_s.so.1|grep
> _Unwind_GetRegionStart
> 00005d0c t __Unwind_GetRegionStart
We are currently discussing it on IRC, but I believe the problem is
that "t" indicates that the symbol is not visible. It should be a "T".
> diff --git a/package/gcc/6.1.0/892-fix-dwarf-fdpic.patch b/package/gcc/6.1.0/892-fix-dwarf-fdpic.patch
> new file mode 100644
> index 0000000..315b406
> --- /dev/null
> +++ b/package/gcc/6.1.0/892-fix-dwarf-fdpic.patch
> @@ -0,0 +1,37 @@
> +Fix DWARF compilation for FDPIC targets
> +
> +Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> +
> +diff -Nur gcc-6.1.0.orig/libgcc/unwind-dw2-fde-dip.c gcc-6.1.0/libgcc/unwind-dw2-fde-dip.c
> +--- gcc-6.1.0.orig/libgcc/unwind-dw2-fde-dip.c 2016-01-04 15:30:50.000000000 +0100
> ++++ gcc-6.1.0/libgcc/unwind-dw2-fde-dip.c 2016-08-05 02:17:40.424195128 +0200
> +@@ -124,7 +124,11 @@
> + {
> + _Unwind_Ptr pc_low;
> + _Unwind_Ptr pc_high;
> ++#if defined __FRV_FDPIC__ || defined __BFIN_FDPIC__
> ++ struct elf32_fdpic_loadaddr load_base;
> ++#else
I'm surprised by this part of the patch, since you are changing the
behavior for __FRV_FDPIC__ as well. It wasn't working before?
In all other chunks you simply add __BFIN_FDPIC__ as behaving the same
as __FRV_FDPIC__ but you're not doing the same here. Is this expected?
> ++#if defined __FRV_FDPIC__ || defined __BFIN_FDPIC__
Obvious question: is there a symbol that says "I'm using FDPIC" and
which would make such conditions simpler?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-05 20:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 19:52 [Buildroot] [RFC][PATCH] bfin: fix two issues with internal toolchain Waldemar Brodkorb
2016-08-05 20:43 ` Thomas Petazzoni [this message]
2016-08-05 22:40 ` Waldemar Brodkorb
2016-08-09 4:39 ` Waldemar Brodkorb
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=20160805224342.1972c673@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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