[cfe-dev] Porting to a new target
Daniel Dilts
diltsman at gmail.com
Mon Jul 7 10:29:28 PDT 2014
>
>
>> 0. QEMU or some other emulator
> Not an absolute must, but super useful if you don't real hardware yet,
> or your hardware doesn't have good debug support.
>
> 1. Compiler (Clang and LLVM)
>>
> 1.25 Linker
> You could port ld, or lld.
> 1.5. Compiler runtimes (libgcc or compiler_rt).
> For compiler_rt, you can probably skip the sanitizers in your first stab
> at it. Save them for after you've got the regular bits working.
> 1.75 Debugger
> Not an absolute must, but suuuuper useful.
> Could port gdb, or lldb.
>
>> 2. C++ library (libc++)
>>
> Or libstdc++
>
> 3. C library (PDCLib?)
>> 4. ABI (libc++abi)
>>
> Or libcxxrt, or libsupc++.
> 5. Unwinder (sort of part of libc++abi, or libgcc_s)
>
I assume that an unwinder is related to stack unwinding when an exception
is thrown. What does that require beyond what libc++abi supports?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140707/c8b3a982/attachment.html>
More information about the cfe-dev
mailing list