search for: apicdrivers

...t; 5*6", but accepts "symbol = 5 * 6" currently. >> Not sure what is easy fix here. >> > > I'm not sure if it is easy, but I think that it's clear that the > linkerscript lexer needs to be improved. I think that is the source of the > problems with `*(.apicdrivers);` as well. > Actually, quickly staring at the code, the `*(.apicdrivers);` seems like it will be lexed correctly. -- Sean Silva > This is not the first bug related to lexing that we have run into (e.g. > lexing `.=` as a single token is the cause of https://llvm.org/bugs/show_ > b...

Hi Dmitry, thanls for sharing. Few comments/questions below: >Here is the list of modifications I had to do in order to link the kernel (I have used llvmlinux with clang and mainline with gcc, the >results are similar): > >1. LLD patches: > - D28094 (Implemented support for R_386_PC8/R_386_8 relocations) Do you remember where it was used ? >5. In

...[0-9]+ On Mon, Jan 23, 2017 at 9:25 AM, George Rimar via llvm-dev < llvm-dev at lists.llvm.org> wrote: > >I'm not sure if it is easy, but I think that it's clear that the > linkerscript lexer needs to be improved. I think that is the source of the > >problems with `*(.apicdrivers);` as well. This is not the first bug > related to lexing that we have run into (e.g. lexing `.=` as a single > >token is the cause of https://llvm.org/bugs/show_bug.cgi?id=31128 ). > > > >-- Sean Silva > > PR31128​ seems to be not an issue. Both gold and bfd do not accep...