Christoffer Lerno
Christoffer Lerno
Do you know what issue that was?
Possibilities: ```c fn void foo() @target("sse4.1") { ... } fn void foo() @target(sse4_1) { ... } ``` If string: ```c fn void foo() @target("v1+sse4.1+ssse3-mmx") { ... } fn void foo()...
It's intended for being able to write for multiple targets in the same compilation. ASM will always ignore instruction limitations.
For the latter, like you can use CPUID to switch between calling function A or B depending on what CPU is detected at startup.
Yeah, so this was the idea. I had some thoughts of doing "target_clone" from GCC, but I think I limit myself to just "target" as there are some challenges making...
I have opened the issue for float128 as #773. I'll close this one since all the others should be done.
Whatever happened to this feature?
I'm curious whether there were any further discussion on this or if it's likely DOA
I am looking at solutions to the Grammar-Kit gradle plugin problem and stumbled over this pull request. It seems interesting for other reasons, but mostly for the codegen .class reading...
This should now work.