-
Notifications
You must be signed in to change notification settings - Fork 508
ObjWriter for armel tizen #3776
Comments
https://github.com/dotnet/llilc/tree/ObjectWriter branch should be up-to-date. @sandreenko Is there anything non-obvious how to get it built? |
In master there is old ObjWriter version, if we build this version with llvm MS brach, we get error:
i.e. in ObjWriter missed SetCodeSectionAttribute function.
I found that, ObjWriter with ObjectWriter branch seems to require latest llvm version from upstream, not MS branch as described in the llilc documentation. With upstream I get only 2 errors:
I found that need some special patch https://reviews.llvm.org/D15334?id=42315#0f5402b0 or a similar patch from the MS branch for this. But all this seems rather confusing ;-) I hope there is a simpler instruction for this. |
Checkout ObjectWriter branch and apply this LLVM patch https://reviews.llvm.org/D29483 |
It was possible to compiler arm32 version. I just thought there was a valid LLVM repository with all needed patches already. Ok, thanks |
@BredPet Can this be closed? |
@tijoytom does it work now? I've tired different combinations of branches but cant build |
The last object writer was published with this llvm version https://github.com/llvm-mirror/llvm What build errors do you see? |
@sandreenko thank you I will try this commit. -#include "llvm/Support/COFF.h"
+#include "llvm/BinaryFormat/COFF.h" If I would revert this commit I will something like this:
|
It helps!
and patch https://reviews.llvm.org/D29483 @sandreenko is it possible to keep this information somewhere in project documentation? I can prepare PR but don't appropriate place. |
After the latest achievements #4856 we would like to clarify the situation with this main component. I. What is the current ObjWriter status, near future? The project looks abandoned. Can any other component be used instead? What are your thoughts on this, if possible, share the details. II. We need to integrate arm and cross-x86 versions into the remote build so CoreRT can use them as well as in the case of x64 architecture. How can we do that? III. Perhaps we need to separate this component as a separate repository so that it's more transparent and not in the LLILC tree as it's now. We understand that it depends on the LLILC and LLVM, but they don't seem to be supported now, too. @Dmitri-Botcharnikov |
I have commented on this here: #4589 (comment)
Agree. Or just add it to this repository as I have mentioned in the comment (not building by default - having default build having dependency on LLVM would be too heavy weight).
I should depend on LLVM only. There should not be any significant LLILC dependency. |
@jkotas thanks for your comments, we will think about this and about integration ObjWriter into CoreRT. |
@BredPet, yes please, that would be excellent! There were some files from CoreCLR as well that objwriter build was requiring, last time I tried. Based on @jkotas' comment, I believe it can be rewired to build independently or with corert sources. Alpine x64, [glibc-]Linux x86 and future platforms/archs/libcs will also benefit from it if |
We tried to build ObjWriter for armel tizen from the current version of https://github.com/dotnet/llilc. But we found that it is too old, in particular there are some sections in CoreRT that are not processed by ObjWriter from this repository. Where can we take more up-to-date version of it with the appropriate building instructions?
The text was updated successfully, but these errors were encountered: