From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 2/5] openrisc: link to libgcc
Date: Mon, 25 Jun 2012 15:00:44 +0200 [thread overview]
Message-ID: <20120625130044.GG14321@pengutronix.de> (raw)
In-Reply-To: <1340628281-8774-3-git-send-email-s.hauer@pengutronix.de>
Hi Franck,
Do you think this patch is ok? It was the easiest way for me to get
__ashrdi3. I don't know how exactly you generated the other library
functions.
On Mon, Jun 25, 2012 at 02:44:38PM +0200, Sascha Hauer wrote:
> To get symbols like __ashrdi3.
>
> Franck started generating these symbols from gcc assembly, which seems
> to be the cleaner approach. The simpler approach for now to get additional
> symbols is to link in libgcc, which is the same as the kernel does.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Franck Jullien <franck.jullien@gmail.com>
> ---
> arch/openrisc/Makefile | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/openrisc/Makefile b/arch/openrisc/Makefile
> index fd8bbbf..1f4b175 100644
> --- a/arch/openrisc/Makefile
> +++ b/arch/openrisc/Makefile
> @@ -1,5 +1,7 @@
> CPPFLAGS += -D__OR1K__ -ffixed-r10 -mhard-mul -mhard-div
>
> +LIBGCC := $(shell $(CC) $(KBUILD_CFLAGS) -print-libgcc-file-name)
> +
> board-$(CONFIG_GENERIC) := generic
>
> KALLSYMS += --symbol-prefix=_
> @@ -18,4 +20,6 @@ common-y += $(BOARD)
> common-y += arch/openrisc/lib/
> common-y += arch/openrisc/cpu/
>
> +common-y += $(LIBGCC)
> +
> lds-y += arch/openrisc/cpu/barebox.lds
> --
> 1.7.10
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-06-25 13:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 12:44 [PATCH] provide ffs and __ashrdi3 for all architectures Sascha Hauer
2012-06-25 12:44 ` [PATCH 1/5] blackfin: add __ashrdi3 Sascha Hauer
2012-06-25 12:44 ` [PATCH 2/5] openrisc: link to libgcc Sascha Hauer
2012-06-25 13:00 ` Sascha Hauer [this message]
2012-06-25 12:44 ` [PATCH 3/5] mips: Add missing ffs include Sascha Hauer
2012-06-25 12:44 ` [PATCH 4/5] nios2: " Sascha Hauer
2012-06-25 12:44 ` [PATCH 5/5] x86: " Sascha Hauer
2012-09-05 20:37 ` [PATCH] [OpenRISC] Add __ashrdi3 and remove link to libgcc Franck Jullien
2012-09-06 6:55 ` Sascha Hauer
2012-09-06 7:28 ` Franck Jullien
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=20120625130044.GG14321@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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