From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-DM] [PATCH V2] dm: mips: Import libgcc components from Linux
Date: Fri, 27 Jul 2012 22:02:47 +0200 [thread overview]
Message-ID: <201207272202.47977.marex@denx.de> (raw)
In-Reply-To: <20120727194509.B71FE203AC0@gemini.denx.de>
Dear Wolfgang Denk,
> Dear Marek Vasut,
>
> In message <1343417017-26346-1-git-send-email-marex@denx.de> you wrote:
> > Import ashldr3, ashrdi3 and lshrdi3 to squash possible libgcc fp
> > mismatch,
>
> > resulting in the following warning:
> ...
>
> > --- a/arch/mips/config.mk
> > +++ b/arch/mips/config.mk
> > @@ -52,3 +52,5 @@ PLATFORM_CPPFLAGS += -msoft-float
> >
> > PLATFORM_LDFLAGS += -G 0 -static -n -nostdlib
> > PLATFORM_RELFLAGS += -ffunction-sections -fdata-sections
> > LDFLAGS_FINAL += --gc-sections
> >
> > +
> > +USE_PRIVATE_LIBGCC = yes
>
> NAK. It is always wrong to mandatorily set this!!
How is that a bug in the toolchain? The u-boot shall be completely self-
contained, am I wrong?
> Best regards,
>
> Wolfgang Denk
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-07-27 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 18:35 [U-Boot] [PATCH] dm: mips: Import libgcc components from Linux Marek Vasut
2012-07-27 19:06 ` Mike Frysinger
2012-07-27 19:10 ` Marek Vasut
2012-07-31 7:56 ` Mike Frysinger
2012-07-27 19:23 ` [U-Boot] [PATCH V2] " Marek Vasut
2012-07-27 19:45 ` [U-Boot] [U-Boot-DM] " Wolfgang Denk
2012-07-27 20:02 ` Marek Vasut [this message]
2012-07-27 20:53 ` Daniel Schwierzeck
2012-07-27 20:59 ` Wolfgang Denk
2012-07-27 21:24 ` Marek Vasut
2012-07-27 22:26 ` Marek Vasut
2012-07-27 20:58 ` Wolfgang Denk
2012-08-19 18:23 ` [U-Boot] " Daniel Schwierzeck
2012-07-27 19:37 ` [U-Boot] [PATCH] " Wolfgang Denk
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=201207272202.47977.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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