From: Avi Kivity <avi@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Issues building seabios
Date: Thu, 19 Nov 2009 15:10:20 +0200 [thread overview]
Message-ID: <4B0543BC.50909@redhat.com> (raw)
Trying to debug the cdrom issue, I see
Compiling whole program out/ccode32.o
src/util.c: In function ‘__end_thread’:
src/util.c:183: internal compiler error: in simplify_subreg, at
simplify-rtx.c:5055
(with F12's gcc (GCC) 4.4.2 20091027 (Red Hat 4.4.2-7))
The issue seems to be with the pos variable; removing everything except
the declaration + initialization retains the error, converting the
variable to static removes it. Presumably you've seen many of these?
With that out of the way, I get:
Linking (no relocs) out/rom32.o
Linking (no relocs) out/rom16.o
Linking out/rom.o
`cdemu_drive' referenced in section `.text32' of out/rom32.o: defined in
discarded section `.discard.var16.src/cdrom.c.107' of out/rom32.o
`cdemu_drive' referenced in section `.text32' of out/rom32.o: defined in
discarded section `.discard.var16.src/cdrom.c.107' of out/rom32.o
`cdemu_drive' referenced in section `.text32' of out/rom32.o: defined in
discarded section `.discard.var16.src/cdrom.c.107' of out/rom32.o
Given we're chasing a cdom related problem, this is suspicious, even
though we aren't using cdemu. Presumably access to uninitialized memory
can confuse disk.c.
out/rom32.o: In function `check_irqs32':
/build/home/tlv/akivity/qemu-kvm/roms/seabios/src/util.c:109: undefined
reference to `trampoline_checkirqs'
No idea where that came from.
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2009-11-19 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 13:10 Avi Kivity [this message]
2009-11-19 13:39 ` [Qemu-devel] Re: Issues building seabios Kevin O'Connor
2009-11-19 14:02 ` Avi Kivity
2009-11-20 22:34 ` Kevin O'Connor
2009-11-26 13:44 ` Avi Kivity
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=4B0543BC.50909@redhat.com \
--to=avi@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).