>Just use LLVM, it's cross platform!
>Dig into it
>Front-ends have to do a shitload of work to get compatibility with different back-ends
>Even languages with massive teams like Rust have absolutely dogshit support for backends that aren't x86 and recent versions of ARM
What the fuck is this shit?

>>105551266 (OP)
>What the fuck is this shit?
A real compiler.

>irrelevant hardware has weak support
ok and

>>105552306
>irrelevant hardware
old arm chipsets outnumber the fuck out of your modern high end hardware

>>105553247
rangeban india
problem solved

>>105553247
And? The difference between rust's tier 1 and 2 is that tier 1 actually mattered to someone enough to set up/donate infrastructure for automated tests to be ran by the rust team.

If you want tier 1, then cough up the dough for it
>that's too much
then it's not actually that important to you, is it? welcome to capitalism

>>105554041
crabs:
>rust architecture support is just fine
5 mins later:
>actually fuck your shit pay me
lamao

>>105554537
>different people think different things?

>>105554568
lamao
good one
https://desuarchive.org/g/thread/105548434/#105551217

>>105554568
>>105554619
(explanation bc you crabs are slow)
(create falseflag thread, personalize op as representing c-ultists)
(5 mins later)
(>but different people think different things)
(exact same pattern as in previous post lamao. counldnt have asked for a better demonstration)

>>105554537
20 minutes is 5 minutes?

>>105554658
>cant even into english comprehension
such is the burden of crabs

if you werent so disagreeable, i would have genuine compassion for you

>>105554643
im not fluent in lisp what does this post say

>stealth Haru thread

>>105551266 (OP)
Didn't care; rape

>>105554643
Based lisp poster

>>105551266 (OP)
I'm also currently building a language on LLVM. Tell me your suffering, anon. Is this about the structs? I just gave up and resorted to passing pointers and using the memcpy intrinsic to get value semantics.

>>105551266 (OP)
Post more Haru.

I just maintain both a gcc makefile and msvc sln file. Shrimple as.

>>105551266 (OP)
usecase for anything other than x64/arm?

>>105558960
writing compute shaders in the same language as your codebase by targeting spir-v

>>105554658
>>105556887
whoever said g is dead is a retard
yous 100% deserved

>>105560868
>SPIR-V eliminates the need for high-level language front-end compilers in device drivers, significantly reducing driver complexity and enabling a broad range of language and framework front-ends to run on diverse hardware architectures and encourages a vibrant ecosystem of open source analysis, porting, debug and optimization tools.
now you got my attention
is spir-v code platform-agnostic?
could i write a game in spir-v? (i have the feeling its gonna be less of a chore than glsl since i come from an opencl background)

>>105551266 (OP)
Just use c or wasm as your IL.

>>105560977
>use c as your il
>all your codegen is infected with c's terrible memory model
no thank you

>>105560913
yeah, but it's also kind of complicated. hence why being able to arbitrarily use a GENERIC COMPILER FRAMEWORK that already has robust target for spir-v would be a huge boon.
https://github.com/KhronosGroup/SPIRV-Guide
unfortunately, llvm ain't it chief.
>opencl
based. i really wish somebody would knock some sense into vendors and force them to knock off all of this cuda and rocm bullshit. there's no reason we should have to use these dogshit vendor lock-in memes when we have perfectly good APIs for compute that are isomorphic with graphics pipelines.

>>105560977
i'd rather use chez scheme than either desu. codegen is easier and debugging it is easier. it's basically the one usecase i've found sexprs tolerable for.
debugging stuff that uses a c as an il is a royal pain in the ass.
debugging stuff on the gpu is already annoying enough without also having to work with machine-generated c and mapping it to another language on top of that.

>>105561401
>c's terrible memory model
has nothing to do with what makes c a mid choice for an il
oh no, arithmetic over addresses? in my abstract machine code? heavens to betsy, save me MIT! aiieee!!!

>>105557302
why not use gnu make on windows?
it's probably a bit of a pain to set up, considering you have to jump through the vc vars hoop, use command.com and have a whole different set of flags. but it's probably less overhead than having a whole .sln to maintain.

microsoft's toolchain seriously sucks lol. i don't know why they require a whole fucking environment to be set up in order to use cl.exe
it's better than the apple situation, but it's still kind of a pain in the ass.

>>105551266 (OP)
If your language cannot compile itself its useless.

>>105562274
all turing complete grammars can do this

>>105551266 (OP)
real life, unfortunately.

>>105561564
>oh no, arithmetic over addresses? in my abstract machine code? heavens to betsy, save me MIT! aiieee!!!
I mean aliasing and all that.

>>105551266 (OP)
ever look into https://c9x.me/compile/ ?

>>105562601
the 9front people never cease to amaze lol

>>105554041
>socialism only when it benefits me
rust-"people" make me fucking sick

>>105561564
the ramblings of a madman

>>105553247
>old arm chipsets outnumber the fuck out of your modern high end hardware
and?
none of them are the same either.

>>105562816
>noooo your heckin language doesn't guarantee correct compilation for my esoteric software float, NEON ARMv5 application CPU that has to use this gay ABI
the real neat part is realizing your shitty C compiler is just as bad and Rust is at least honest about it.

lucky for most you dipshits though, even well out of life parts still in use are all armv7l parts and they're probably all running bog standard linux 4.9, with the GNU EABI and have a hardware float with most all the basic features, like NEON.

>>105563397
>hurr
>more durr at 9

>>105562816
what? who mentioned socialism?

>he fell for the llvmeme
GCChads won