[LLVMdev] [PATCH][RFC] HSAIL Target
JF Bastien
jfb at google.com
Tue Jun 30 19:34:21 PDT 2015
>
> One of the important property of MC is avoiding the need for two code
> paths in the code generator.
>
> If MC cannot support the format you need, we should work on fixing that in
> a way that maintains the property that most code is shared when writing
> objects or assembly. This is a need that is shared by Webassembly I think.
>
>
> My suggestion would be to start with just the assembly printing path and
> work to figure out what needs to happen in MC.
>
>
> It will take a long time to come up with a replacement for emitting BRIG
> in MC. How blocking of an issue is this to getting this committed? If
> really necessary, I can strip out the BRIG stuff, but would need to
> constantly maintain a patch re-adding it on top of trunk which would be a
> huge hassle so I would rather not.
>
Dan and I have talked to a few folks who have given us the same feedback
for WebAssembly: we should consider using MC for virtual ISA emission, even
though it isn't quite suitable as it exists in LLVM today. It's an
opportunity to fix LLVM. Dan and I don't know much about MC, but we are
going to explore this route.
I have no opinion on how this should affect HSAIL's current patch. Dan and
I are willing to take the lead on this, and would be happy to work with
other virtual ISAs to make sure architectural changes to MC make sense for
their usecases.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150630/bfe1c19b/attachment.html>
More information about the llvm-dev
mailing list