From: Tim Deegan <tim@xen.org>
To: Jeffrey Karrels <karrelsj@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Clang/LLVM version requirements
Date: Fri, 7 Sep 2012 09:50:36 +0100 [thread overview]
Message-ID: <20120907085036.GA71093@ocelot.phlegethon.org> (raw)
In-Reply-To: <CAFw--Dd0k7L+T_UJc0yHAkUGrY_-GDHaQjK3OM-1UdOp=J-wAQ@mail.gmail.com>
At 15:32 -0700 on 06 Sep (1346945573), Jeffrey Karrels wrote:
> Is there a required Clang and LLVM version one needs to do a 'make
> xen-dist clang=y'?
>
> I recently tried and the process failed. I haven't begun debugging as
> I figured I would ask the obvious first. The build failed with the
> following:
Looks like the clang build has bitrotted a little - sorry. It's too
late to fix this for 4.2 now but we can sort it out after we branch
(i.e. next week) and backport any build fixes for 4.2.1.
I have:
Debian clang version 3.0-6 (tags/RELEASE_30/final) (based on LLVM 3.0)
Target: x86_64-pc-linux-gnu
Thread model: posix
which can build _almost_ everything but chokes on a new .subsection rune
in inline asm. It builds and boots with the change below. Building
lto=y isn't working (GOLD is choking on the final link). I'll look into
that next week.
Jan, would you object to some other way of checking for .bss in reloc.c?
Could we just objcopy it out so any BSS symbols make it fail at link
time? In any case we probably ought to check for stray .data symbols too.
Cheers,
Tim.
diff -r ec23c2a11f6f xen/arch/x86/boot/reloc.c
--- a/xen/arch/x86/boot/reloc.c Thu Sep 06 17:08:44 2012 +0100
+++ b/xen/arch/x86/boot/reloc.c Fri Sep 07 09:30:13 2012 +0100
@@ -18,10 +18,7 @@ asm (
" call 1f \n"
"1: pop %ebx \n"
" mov %eax,alloc-1b(%ebx) \n"
- " mov $_end,%ecx \n" /* check that BSS is empty! */
- " sub $__bss_start,%ecx \n"
- " jz reloc \n"
- "1: jmp 1b \n"
+ " jmp reloc \n"
);
/* This is our data. Because the code must be relocatable, no BSS is
@@ -30,9 +27,6 @@ asm (
asm (
"alloc: \n"
" .long 0 \n"
- " .subsection 1 \n"
- " .p2align 4, 0xcc \n"
- " .subsection 0 \n"
);
typedef unsigned int u32;
next prev parent reply other threads:[~2012-09-07 8:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 22:32 Clang/LLVM version requirements Jeffrey Karrels
2012-09-07 8:50 ` Tim Deegan [this message]
2012-09-07 10:04 ` Jan Beulich
2012-09-13 10:11 ` Tim Deegan
2012-09-13 11:52 ` Jan Beulich
2012-09-13 12:21 ` Tim Deegan
2012-09-13 14:01 ` Jan Beulich
2012-09-13 14:55 ` Tim Deegan
2012-09-13 15:05 ` Keir Fraser
2012-09-13 15:09 ` Keir Fraser
2012-09-13 15:27 ` Ian Campbell
2012-09-13 15:51 ` Keir Fraser
2012-09-13 15:22 ` Jan Beulich
2012-09-13 15:34 ` Keir Fraser
2012-09-13 15:06 ` Jan Beulich
2012-09-13 12:40 ` Paolo Bonzini
2012-09-13 14:04 ` Jan Beulich
2012-09-13 14:13 ` Paolo Bonzini
2012-09-13 14:18 ` Jan Beulich
2012-09-07 15:58 ` Jeffrey Karrels
2012-09-11 18:43 ` Jeffrey Karrels
2012-09-12 10:24 ` Stefano Stabellini
2012-09-13 16:15 ` Ian Jackson
2012-09-13 16:41 ` Tim Deegan
2012-09-13 17:04 ` Ian Jackson
2012-09-12 10:31 ` Tim Deegan
2012-09-12 10:38 ` Ian Campbell
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=20120907085036.GA71093@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=karrelsj@gmail.com \
--cc=xen-devel@lists.xen.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).