From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data
Date: Fri, 1 Jan 2010 22:14:32 -0500 [thread overview]
Message-ID: <201001012214.50112.vapier@gentoo.org> (raw)
In-Reply-To: <OF127ADDB2.588B4488-ONC125769E.0058B6C5-C125769E.005A9C05@transmode.se>
On Friday 01 January 2010 11:29:41 Joakim Tjernlund wrote:
> Mike Frysinger <vapier@gentoo.org> wrote on 01/01/2010 07:18:44:
> > yes, but that doesnt mean gcc takes care of inlining all of printf_puts()
> > into the puts() and all the new call sites go to puts()
>
> Sure, gcc might not inline the current code in this case. I guess
> you don't want the extra size this would incur or is there some else you
> are concerned about?
the extra size
> > i dont have any plans on wanting this, and it seems pretty invasive ...
> > and easy to introduce new code that breaks PIC people but no one else
> > really notices ...
>
> Yes, it is a bit invasive hence the question if this is acceptable to
> u-boot. I have been looking for other ways to do this but there isn't one
> sans modifying gcc. You are sort of an gcc guy, what do you think the odds
> are
> that gcc would add a few new options mainly useful for smaller
> embedded progs like u-boot (and possible the kernel too)?
i'm not really a gcc guy ... i just sometimes fake it. i honestly dont have
an idea here how they would respond.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100101/9c19df64/attachment.pgp
next prev parent reply other threads:[~2010-01-02 3:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 15:08 [U-Boot] [PATCH 0/4] Make u-boot true PIC for ppc Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 1/4] ppc: Add const void *link_off(const void *addr) Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 3/4] Use LINK_OFF in enviroment too Joakim Tjernlund
2009-12-30 15:08 ` [U-Boot] [PATCH 4/4] ppc: Make mpc83xx start.S relative Joakim Tjernlund
2009-12-31 18:44 ` [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data Mike Frysinger
2010-01-01 1:39 ` Joakim Tjernlund
2010-01-01 6:18 ` Mike Frysinger
2010-01-01 16:29 ` Joakim Tjernlund
2010-01-02 3:14 ` Mike Frysinger [this message]
2010-01-02 18:17 ` Wolfgang Denk
2010-01-03 10:48 ` Joakim Tjernlund
2010-01-02 18:13 ` Wolfgang Denk
2010-01-03 10:33 ` Joakim Tjernlund
2010-01-03 19:51 ` Wolfgang Denk
2010-01-03 20:06 ` Albert ARIBAUD
2010-01-03 20:17 ` Wolfgang Denk
2010-01-03 20:41 ` Albert ARIBAUD
2010-01-03 21:07 ` Wolfgang Denk
2010-01-04 6:54 ` Albert ARIBAUD
2010-01-03 22:29 ` Graeme Russ
2010-01-05 20:20 ` Scott Wood
2010-01-05 22:11 ` Joakim Tjernlund
2010-01-06 21:02 ` Scott Wood
2010-01-04 1:08 ` Joakim Tjernlund
2010-01-05 0:40 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2009-11-02 18:01 [U-Boot] [PATCH 0/4] Make u-boot true PIC for ppc Joakim Tjernlund
2009-11-02 18:01 ` [U-Boot] [PATCH 1/4] ppc: Add const void *link_off(const void *addr) Joakim Tjernlund
2009-11-02 18:01 ` [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data Joakim Tjernlund
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=201001012214.50112.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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