[llvm-dev] How to make when developing machine function pass ?

[Reid Kleckner via llvm-dev]

The google groups link seems to work for me, but is broken when I am not
logged into my Google account. >_> I mean this thread titled "debug build
busts memory":
http://llvm.1065342.n5.nabble.com/llvm-dev-debug-build-busts-memory-td133229.html#a133237

On Tue, Mar 10, 2020 at 10:44 AM Reid Kleckner <rnk at google.com> wrote:

> One minute to recompile and relink one file is too long. There are ways to
> make incremental development significantly faster, and there have been a
> few threads about this on llvm-dev. This one came to mind:
> https://groups.google.com/g/llvm-dev/c/ur-2aX_KvfM/m/FFRlZdZECAAJ
> If you search around, you can find some of the standard recommendations:
> - Use ninja instead of make
> - Use lld or gold instead of ld.bfd
> - Adjust debug info settings (-gmlt, split dwarf, or disable it)
> - Use external tablegen (probably not your problem)
>
> Good luck!
>
> On Mon, Mar 9, 2020 at 3:31 AM PenYiWang via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi
>>
>> I am modifying X86RetpolineThunks.cpp.
>>
>> X86RetpolineThunks.cpp 's location is llvm-src/lib/Target/X86.
>>
>> Which target should I use , next time use clang test.c , I can see the
>> difference .
>>
>> I found that  "make llc"  doesn't work.
>>
>> And either "make LLVMX86CodeGen" doen't work.
>>
>> "make clang" waste a lot of time, even -j64.
>>
>> Every time modifying the file of machine function pass ,
>> I have to wait for 1 min.
>>
>> It drive me crazy.
>>
>> Which "target" should use to "make" when developing machine function pass
>> ?
>>
>> Or is  there other way to develop machine function pass?
>>
>> Thank you.
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200310/c6b5c7d8/attachment.html>