All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@colin2.muc.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Andi Kleen <ak@muc.de>,
	akpm@osdl.org, jh@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix compilation on gcc 3.4
Date: 14 Jan 2004 09:58:25 +0100
Date: Wed, 14 Jan 2004 09:58:25 +0100	[thread overview]
Message-ID: <20040114085825.GA10916@colin2.muc.de> (raw)
In-Reply-To: <20040114084721.GP31589@devserv.devel.redhat.com>

On Wed, Jan 14, 2004 at 03:47:22AM -0500, Jakub Jelinek wrote:
> On Wed, Jan 14, 2004 at 09:37:00AM +0100, Andi Kleen wrote:
> > 
> > The upcomming gcc 3.4 has a new inlining algorithm which sometimes
> > fails to inline some "dumb" inlines in the kernel. This sometimes leads
> > to undefined symbols while linking.
> 
> It fails to inline routines with always_inline attribute?
> That sounds like a gcc bug.  always_inline should mean inline always,
> and issue error if for some reason it is impossible.

The problem is that there are some functions that are declared
inline in header files, but there is no body available. When they are
called this ends with an hard error in gcc. I started with fixing
them but eventually gave up because there were so many of them.

In addition you get tons of ugly warnings.

-Andi

  reply	other threads:[~2004-01-14  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14  8:37 [PATCH] Fix compilation on gcc 3.4 Andi Kleen
2004-01-14  8:47 ` Jakub Jelinek
2004-01-14  8:58   ` Andi Kleen [this message]
2004-01-14 10:53     ` Jan Hubicka
2004-01-14  8:49 ` Andrew Morton
2004-01-14  9:04   ` Andi Kleen

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=20040114085825.GA10916@colin2.muc.de \
    --to=ak@colin2.muc.de \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=jakub@redhat.com \
    --cc=jh@suse.cz \
    --cc=linux-kernel@vger.kernel.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.