CC on SH: still working on FPU and long-long types; idly wonders if there would be any point in supporting __int128 and __float128 on SH4...
I don't consider there to be any point to supporting __int128 on any arch, and IEEE quad only if it's the ABI long double.
-
-
it is rare but "sometimes" useful; though not usually supported on 32-bit archs by most compilers. debate is whether to have runtime stubs.
-
another idle debate: for struct copy; at which size to fall back to memcpy, or whether to use dedicated runtime calls for some size ranges.
-
As-Is: Al>=4,Sz<=16: inline copy; Al>=4,Sz<=64: dedicated copy func; Sz<=4: inline copy (byte/word); else call generic memcpy...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.