Tim Northover
2013-Nov-26 18:13 UTC
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
>> Out of curiosity, can't clang do the assembly itself in this case? > > It can, but you need to use -integrated-as, because that's not the default > yet. (some missing features).Do you remember what those features are Renato? MC has been around years, we really should start sorting them now. Cheers. Tim
Greg Fitzgerald
2013-Nov-26 18:46 UTC
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
Here's where we left off: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-February/059099.html In 3.4, I think the integrated assembler is in excellent shape and should be enabled by default for ARM ELF. I've been using it exclusively for at least 6 months now. -Greg On Tue, Nov 26, 2013 at 10:13 AM, Tim Northover <t.p.northover at gmail.com> wrote:>>> Out of curiosity, can't clang do the assembly itself in this case? >> >> It can, but you need to use -integrated-as, because that's not the default >> yet. (some missing features). > > Do you remember what those features are Renato? MC has been around > years, we really should start sorting them now. > > Cheers. > > Tim > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Tim Northover
2013-Nov-26 19:00 UTC
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
On 26 November 2013 18:46, Greg Fitzgerald <garious at gmail.com> wrote:> Here's where we left off: > http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-February/059099.htmlBack then you mentioned a Chromium build, are you still running that routinely with -integrated-as? That would give a reasonable reassurance about general-usage, if not weird features. Cheers. Tim.
Renato Golin
2013-Nov-26 19:02 UTC
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
On 26 November 2013 18:13, Tim Northover <t.p.northover at gmail.com> wrote:> Do you remember what those features are Renato? MC has been around > years, we really should start sorting them now. >No. I remember there were issues, but I never catalogued them. I agree we should move as soon as possible, and there's nothing holding me of doing it. I think post-3.4 we can cope with the consequences if they come, since it seems nobody remembers what they were in the first place. ;) --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131126/f8103dca/attachment.html>
Tim Northover
2013-Nov-26 19:14 UTC
[LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
> I think post-3.4 we can cope with the consequences if they come, since it > seems nobody remembers what they were in the first place. ;)Looks like there might be a handful of .eabi_attribute variantswe can't handle (http://llvm.org/bugs/show_bug.cgi?id=15172) -- ones involving a string? Cheers. Tim.
Reasonably Related Threads
- [LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
- [LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
- [LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
- [LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang
- [LLVMdev] Targeting ARM Cortex-a9 from x86_64 with clang