All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: David Miller <davem@davemloft.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Fix kernel builds with newer gcc versions and -Os
Date: Fri, 02 May 2008 16:45:45 -0500	[thread overview]
Message-ID: <481B8B89.2030703@freescale.com> (raw)
In-Reply-To: <20080502.144220.53637856.davem@davemloft.net>

David Miller wrote:
> If you link in libgcc, all of a sudden you have a whole new class of
> potential problems, don't do it.
> 
> All it takes is one of these libgcc libcalls the kernel actually
> references, needing something else in libc, to make this exercise
> futile.

What in libgcc references libc, and why isn't this a problem for 
Linux/ARM, Linux/SH, U-boot, and the many other libc-less programs that 
use libgcc?

-Scott

  reply	other threads:[~2008-05-02 21:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:21 [PATCH] [POWERPC] Fix kernel builds with newer gcc versions and -Os Kumar Gala
2008-05-02 15:07 ` Scott Wood
2008-05-02 15:26   ` Kumar Gala
2008-05-02 17:34     ` Segher Boessenkool
2008-05-02 21:34       ` Kumar Gala
2008-05-02 21:40         ` Scott Wood
2008-05-02 21:42         ` David Miller
2008-05-02 21:45           ` Scott Wood [this message]
2008-05-02 22:04             ` David Miller
2008-05-02 22:16               ` Scott Wood
2008-05-02 22:30                 ` David Miller
2008-05-02 22:38                   ` Scott Wood
2008-05-02 22:39                     ` David Miller
2008-05-03  0:15               ` Segher Boessenkool
2008-05-02 23:24           ` Benjamin Herrenschmidt
2008-05-02 23:23         ` Benjamin Herrenschmidt
2008-05-08  6:26         ` Paul Mackerras
2008-05-02 17:33 ` Segher Boessenkool
2008-05-02 21:31   ` Kumar Gala

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=481B8B89.2030703@freescale.com \
    --to=scottwood@freescale.com \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.