All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: undefined reference to __udivdi3 (gcc-4.3)
Date: Sun, 04 May 2008 11:35:20 -0600	[thread overview]
Message-ID: <481DF3D8.3010108@shaw.ca> (raw)
In-Reply-To: <fa.QTbvQYXhEm5VNP5dvkl5JG7NHYQ@ifi.uio.no>

Christian Kujau wrote:
> Hi,
> 
> while trying to compile current -git or 2.6.25.1 with gcc (Debian 
> 4.3.0-4) 4.3.1 20080501 (prerelease), the following error occurs during 
> linking:
> 
> arch/x86/xen/built-in.o: In function `xen_timer_interrupt':
> time.c:(.text+0x2992): undefined reference to `__udivdi3'
> time.c:(.text+0x2a13): undefined reference to `__udivdi3'
> make: *** [.tmp_vmlinux1] Error 1
> 
> 
> Searching the archives brought up old issues with gcc-3.4 [0] and not so 
> old posting from 01/2008 [1], but I could not find a solution (or a 
> consense about (not to) include libgcc.a).
> 
> Full make.log and .config: http://nerdbynature.de/bits/2.6.25.1/xen/
> 
> Hints welcome :)
> 
> Thanks,
> Christian.
> 
> [0] http://gcc.gnu.org/ml/gcc/2004-01/msg01975.html
> [1] http://www.nabble.com/gcc-4.3:-Kernel-build-fails-td15135607.html

I assume it's one or both of these loops in arch/x86/xen/time.c 
do_stolen_accounting() that are being optimized into a divide which 
generates a libgcc call:

	while (stolen >= NS_PER_TICK) {
		ticks++;
		stolen -= NS_PER_TICK;
	}

or

	while (blocked >= NS_PER_TICK) {
		ticks++;
		blocked -= NS_PER_TICK;
	}

I seem to recall in one previous case we added some dummy assembly code 
to stop gcc from doing this. Not sure if that is a sustainable fix, though..

       reply	other threads:[~2008-05-04 17:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.QTbvQYXhEm5VNP5dvkl5JG7NHYQ@ifi.uio.no>
2008-05-04 17:35 ` Robert Hancock [this message]
2008-05-04 22:19   ` undefined reference to __udivdi3 (gcc-4.3) Segher Boessenkool
2008-05-07  9:29     ` Jeremy Fitzhardinge
2008-05-08 15:16       ` [PATCH] common implementation of iterative div/mod Jeremy Fitzhardinge
2008-05-08 20:26         ` Andrew Morton
2008-05-08 22:00           ` Jeremy Fitzhardinge
2008-05-08 20:52         ` Segher Boessenkool
2008-05-08 21:57           ` Jeremy Fitzhardinge
2008-05-09 11:45         ` Christian Kujau
2008-05-14  6:46         ` Andrew Morton
2008-05-14  7:33           ` Jeremy Fitzhardinge
2008-05-14  8:33             ` Andi Kleen
2008-05-14  9:55               ` Jeremy Fitzhardinge
2008-05-14 10:50                 ` Andi Kleen
2008-05-14 10:52                   ` Jeremy Fitzhardinge
2008-05-14 11:21                     ` Andi Kleen
2008-05-14 12:58                       ` Jeremy Fitzhardinge
2008-05-04 10:59 undefined reference to __udivdi3 (gcc-4.3) Christian Kujau

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=481DF3D8.3010108@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.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 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.