[llvm-dev] Linking Linux kernel with LLD
Sean Silva via llvm-dev
llvm-dev at lists.llvm.org
Wed Feb 1 14:10:06 PST 2017
On Sat, Jan 28, 2017 at 9:57 AM, Dmitry Golovin <dima at golovin.in> wrote:
> At this point I'm able to link Linux kernel with LLD and objcopy doen't
> give me any errors.
> The versions are:
> Linux 4.10.0-rc5 (+ applied the patch from my previous message)
> LLD 5.0.0 (https://github.com/llvm-mirror/lld
> db83a5cc3968b3aac1dbe3270190bd3282862e74) (+ applied D28612)
> GNU objcopy (GNU Binutils) 2.27
> The problem is that the resulting kernel doesn't boot. Does anybody have
> any suggestions on how to debug it or any guesses what did go wrong while
As far as different things that can go wrong, some things to consider:
- LLD's output binary has the same (or similar) data as the BFD/gold output
binary. E.g. if the LLD binary is only half as big (or the PT_LOAD's that
the booloader looks at are half as bit), LLD might not be putting things
into the output or into the right output sections.
- The bootloader is looking for something in the dynamic symbol table, but
it isn't there. LLD might be resolving symbols differently.
- Section contents are different between LLD and BFD/gold. E.g. for freebsd
there is a "linker set" section which contains pointers to a bunch of
metadata structs that are needed. LLD was not relocating these correctly
because the symbols were not ending up in the output or something like that
(I forget exactly; Michael might remember better).
-- Sean Silva
> 28.01.2017, 05:48, "Sean Silva via llvm-dev" <llvm-dev at lists.llvm.org>:
> On Fri, Jan 27, 2017 at 1:31 PM, Rui Ueyama <ruiu at google.com> wrote:
> So as you noticed that linker script tokenization rule is not very trivial
> -- it is context sensitive. The current lexer is extremely simple and
> almost always works well. Improving "almost always" to "perfect" is not
> high priority because we have many more high priority things, but I'm fine
> if someone improves it. If you are interested, please take it. Or maybe
> I'll take a look at it. It shouldn't be hard. It's probably just a half day
> Yeah. To be clear, I wasn't saying that this was high priority. Since I'm
> complaining so much about it maybe I should take a look this weekend :)
> As far as I know, the grammar is LL(1), so it needs only one push-back
> buffer. Handling INCLUDE directive can be a bit tricky though.
> Maybe we should rename ScriptParserBase ScriptLexer.
> That sounds like a good idea.
> -- Sean Silva
> On Fri, Jan 27, 2017 at 11:17 AM, Rafael Avila de Espindola <
> rafael.espindola at gmail.com> wrote:
> > Hmm..., the crux of not being able to lex arithmetic expressions seems to
> > be due to lack of context sensitivity. E.g. consider `foo*bar`. Could be
> > multiplication, or could be a glob pattern.
> > Looking at the code more closely, adding context sensitivity wouldn't be
> > that hard. In fact, our ScriptParserBase class is actually a lexer (look
> > the interface; it is a lexer's interface). It shouldn't be hard to change
> > from an up-front tokenization to a more normal lexer approach of scanning
> > the text for each call that wants the next token. Roughly speaking, just
> > take the body of the for loop inside ScriptParserBase::tokenize and add a
> > helper which does that on the fly and is called by consume/next/etc.
> > Instead of an index into a token vector, just keep a `const char *`
> > that we advance.
> > Once that is done, we can easily add a `nextArithmeticToken` or something
> > like that which just lexes with different rules.
> I like that idea. I first thought of always having '*' as a token, but
> then space has to be a token, which is an incredible pain.
> I then thought of having a "setLexMode" method, but the lex mode can
> always be implicit from where we are in the parser. The parser should
> always know if it should call next or nextArithmetic.
> And I agree we should probably implement this. Even if it is not common,
> it looks pretty silly to not be able to handle 2*5.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev