From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2 V2] Move libgcc inclusion from common Makefile to platform configs files
Date: Sat, 20 Jun 2009 19:15:47 +0200 [thread overview]
Message-ID: <20090620171547.GN3849@game.jcrosoft.org> (raw)
In-Reply-To: <200906201159.59936.vapier@gentoo.org>
> > > >
> > > > This is where I disagree other arch as mips and other will also need to
> > > > move away from the needs to include libgcc to be really toolchain
> > > > independant
> > > >
> > > > I do think it's really important for U-Boot be able to have full
> > > > control to have a functions embedded into.
> > > >
> > > > So stop to have libgcc include by default will really reflect it
> > >
> > > so you have two arches (mips/arm) that you dont want to use libgcc. that
> > > is still vastly the minority. if we ever do get most ports not using
> > > libgcc, then pushing it to the arch configs makes sense. but we havent
> > > and we arent even close.
> >
> > which minoroty?
>
> the majority use libgcc
>
> > I just give you example but you will see arm, mips, sh, powerpc etc...
> > toolchains problem just because we use the libgcc
>
> 4 is still the minority, but this is Woflgang's call
>
> > I've patch in qualification for mips and sh so it will not be so long
> > maybe 2 or 3 weeks
>
> considering my proposed change is much simpler, and would allow for trivial
> migration as you converted things, it still makes more sense.
it's not the size of the change, it's just I do not agree with it
Best Regards,
J.
next prev parent reply other threads:[~2009-06-20 17:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 9:33 [U-Boot] [PATCH 1/2 V2] Move libgcc inclusion from common Makefile to platform configs files Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 9:33 ` [U-Boot] [PATCH 2/2 V2] ARM: Don't include libgcc anymore Jean-Christophe PLAGNIOL-VILLARD
2009-06-21 12:25 ` Dirk Behme
2009-06-20 10:18 ` [U-Boot] [PATCH 1/2 V2] Move libgcc inclusion from common Makefile to platform configs files Mike Frysinger
2009-06-20 10:40 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 11:08 ` Mike Frysinger
2009-06-20 11:30 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 12:57 ` Mike Frysinger
2009-06-20 13:01 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 13:33 ` Mike Frysinger
2009-06-20 13:57 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 15:59 ` Mike Frysinger
2009-06-20 17:15 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-07-10 22:27 ` Wolfgang Denk
2009-06-22 18:55 ` Scott Wood
2009-07-04 21:52 ` 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=20090620171547.GN3849@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--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