From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: linux-2.6.18-xen.hg compilation issue with gcc 4.3
Date: Wed, 21 May 2008 15:19:19 +0200 [thread overview]
Message-ID: <48342157.7090907@inria.fr> (raw)
Hello.
The linux-2.6.18-xen.hg kernel fails to build with gcc 4.3, in linking
stage:
arch/i386/kernel/built-in.o: In function `sync_xen_wallclock':
time-xen.c:(.text+0x6141): undefined reference to `__udivdi3'
time-xen.c:(.text+0x618a): undefined reference to `__udivdi3'
arch/i386/kernel/built-in.o: In function `do_settimeofday':
(.text+0x63bd): undefined reference to `__udivdi3'
arch/i386/kernel/built-in.o: In function `do_settimeofday':
(.text+0x640b): undefined reference to `__udivdi3'
arch/i386/kernel/built-in.o: In function `do_settimeofday':
(.text+0x6489): undefined reference to `__udivdi3'
arch/i386/kernel/built-in.o:(.text+0x64d2): more undefined references to
`__udivdi3' follow
According to LKM, this is a known issue:
http://www.nabble.com/undefined-reference-to-__udivdi3-(gcc-4.3)-td17045078.html
However, I couldn't find any loop susceptible to be wrongly optimised in
incriminated code (sync_xen_wallclock in arch/i386/kernel/time-xen.c).
Any hint welcome.
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62
next reply other threads:[~2008-05-21 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 13:19 Guillaume Rousse [this message]
2008-05-21 13:45 ` linux-2.6.18-xen.hg compilation issue with gcc 4.3 Keir Fraser
2008-05-21 15:22 ` Guillaume Rousse
2008-05-21 15:45 ` Keir Fraser
2008-05-21 15:48 ` Guillaume Rousse
2008-05-21 13:49 ` Jan Beulich
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=48342157.7090907@inria.fr \
--to=guillaume.rousse@inria.fr \
--cc=xen-devel@lists.xensource.com \
/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.