Eddy S.
Eddy S.
ahhh nice to know. :+1:
is this also true for primitive datatypes like `i32`? in this case it means there is no feasible way to return results to qml without building a custom `garbagecollection`-mechanism.
so I had a little time to investigate: The [slot definition](https://filcuc.github.io/DOtherSide/struct_slot_definition.html#a355e9a546c9913fd89d21d419a3c5092) struct has a field for the return type of the slot. In the Q_OBJECT macro this return value is...
i think it is obvious that this subject needs much more thought and the pr needs rework. For now I will mark this PR ad draft and rework it.
opened PR #1057 which adds vectorized crc32 for s390x platform
So, I started working on the S390X deflate/inflate optimization patch and would like to ask for the preferred review mode: should I try to split it into multiple easy reviewable...
@iii-i IMHO i don't see any point in keeping the old 32(31) bit code. the compat mode got removed from [the kernel](https://lore.kernel.org/all/[email protected]/) and glibc is also slowly [shutting 31bit support...
Hi, @Dead2 yes `S390` means 31-Bit and `S390X` means 64-Bit. But take it with a grain of salt! glibc for example called the 64bit branch `s390-64`. And llvm call it...