inkyoto

45 ms·

571.
by inkyoto 4y ago
> We won't get cleaner buses by magically wishing all the passengers to have better hygiene. Isn't wearing different clothes indoor and outdoor the actual solution? We can't expect public spaces leave alone the public tran
572.
by inkyoto 4y ago
Varities of Chinese and Japanese green teas differ in their processing techniques so much that they require different preparation techniques as well. They possess distinctly different flavours, too. Most Japanese green teas are steamed past
573.
by inkyoto 4y ago
There are also (rare nowadays and are mostly available in higher end / performance cars but used to be more frequent in late 80's and 90's): FF 4WS FR 4WS 4WS is for «four wheel steering» (the emphasis is on «steering», not «
574.
by inkyoto 4y ago
> When should you use Kafka instead of storing rows in SQL with a timestamp so you can replay them/fetch them if needed? When the use case warrants it and when downstream consumers need to be notified of a change in the data or its
575.
by inkyoto 4y ago
> […] and GCC was far less sophisticated With all due respect, this is simply not true. Especially for the time, GCC was the most sophisticated compiler out there, and the only one that could be easily retargeted to a new or another plat
576.
by inkyoto 4y ago
That is a very frivolous interpretation of what I said. I was comparing: a) 32-bit MIPS CPU's with 64-bit MIPS CPU's, b) 32-bit SPARC v8 and 64-bit SPARC v9 (UltraSPARC) CPU's, and c) performance of 32-bit RISC CPU's c
577.
by inkyoto 4y ago
To be crystal clear: my statement pertained to 32-bit MIPS CPU's and MIPS CPU's predating the R8000. They were very slow. 32-bit MIPS CPU's did not have multiply and division instructions, they had branch delay slots that are
578.
by inkyoto 4y ago
> The runtime doesn't know all that much […] If we are talking about JIT, yes, it does, for it instruments the runtime, gathers the information about hot code paths and performs the in-place optimisation. Think of the profile guide
579.
by inkyoto 4y ago
Out of three VLIW architectures I have looked into, 2x (Elbrus and Itanium) rely on the predication heavily. i860 does not have instruction predicates. Predication places the burden of creating optimal instruction bundles AND the correct hi
580.
by inkyoto 4y ago
To be completely honest, MIPS CPU's had never been known for their speed – not until the release of the 64-bit MIPS architecture anyway when they finally became competitive with other RISC CPU's, but it was a complete ISA redesign
581.
by inkyoto 4y ago
Indeed. RISC-V instruction fusion is a little bit VLIW like. I wonder how it handles the fused instruction transition across CPU cores tho (I have not looked into it).
582.
by inkyoto 4y ago
Yeah, by mid-2000s most RISC workstations (Alpha, Sun, SGI, PowerPC tho not IBM POWER and certainly not the top of the range datacentre class servers) had converged on the mainstream PC architecture, e.g. a PCI bus, EIDE disk controllers, s
583.
by inkyoto 4y ago
Itanium was a second Intel VLIW design. The first one was the i860, which was a mixed bag of either being eye popping fast, if instruction bundles were handcrafted by a human, or being as slow as a dog if it was a compiler that emitted the
584.
by inkyoto 4y ago
This is a somewhat myopic take on the value of the dynamic linking. One important aspect is that a dynamic library provides a host of implementations that have been tailored or optimised for specific subsets of CPU's or specific genera
585.
by inkyoto 4y ago
What exactly is the credibility of Robert Lindsay who describes themselves as: «BA Journalism […] teaching credential. Political activist, linguist, amateur cold case murders sleuth, psychological counselor (!), long-time K-12 schoolteach
586.
by inkyoto 4y ago
Ignorance is a bliss, and your linguistic and historical ignorance is admirable as well as it continues to push new limits. Russian, as a distinct language, is a fairly recent historical development that is slightly over 400 years old, and
587.
by inkyoto 4y ago
> Nope. Ukraine is the original Russia, now called Kievan Rus by RF. False. As per historical findings, the current scientific consensus is that the origins of the Rus people (who ruled Kyiv/Kiev/Kievan Rus') are traced ba
588.
by inkyoto 4y ago
> A lot of words to repeat Russian propaganda. Duly noted. Ignorance, the lack of historical as well as linguistic knowledge, and the lack of reputable and verifiable counterpoints on your behalf is now officialy Russian propaganda. >
589.
by inkyoto 4y ago
With all due respect, historical and linguistic assertions are borderline nonsense. > Ukrainian language is closer to Czech and Slovak than to Russian. Ukrainian culture is closer to Polish and Slovak culture than Russian. Which Ukrainia
590.
by inkyoto 4y ago
It is not about the underlying database structure, it is about complex, "branchy" relations and querying them, including properties of the relations themselves. Relational databases are not good with recursive join queries made ag
591.
by inkyoto 4y ago
Thruppence is a somewhat inconvenient coin to pay with at a toll booth from a vehicle travelling at the 133619.661 furlongs per fortnight speed. It helps to travel prepared and dispense the required number of thruppence into little cloth ba
592.
by inkyoto 4y ago
> We are perfectly adapted for a part of Africa and that's pretty much it. Not the British or the Irish. These particular designs have not been contrived to withstand ambient temperatures exceeding +20C, with a very low degree of he
593.
by inkyoto 4y ago
This is excellent, thank you. I was under the impression that the compressed instructions set required a dedicated compiler switch, and counted a number of instructions instead. Now that «X is 18% smaller than Y» is quantified, there is th
594.
by inkyoto 4y ago
So what is the gcc (or gas via gcc) compiler switch to make the RISC-V compiler backend yiled compressed instructions? I have been unable to find a working one in the documentation, and the beehive mind has been of no help either.
595.
by inkyoto 4y ago
For the sake of savouring a civilised nerdy discourse, may we stick to the same code and set a rule that only compiler switches can be fiddled with? Comparing 3 lines (after discarding empty lines, curly braces, functions and variable decla
596.
by inkyoto 4y ago
I am more than happy to stand corrected, if a correction is warranted. What is the gcc 12.2.0 -march= value to make gcc 12.2.0 emit the compressed 64-bit code? The gcc 12.2.0 rejects all the -march RISC-V values the gcc documentation cite
597.
by inkyoto 4y ago
And that is why I used the same compiler for all ISA's: gcc 12.2.0. The GIMPLE IR intermediate product is the same for all architectures; however, the ISA backend is specific to each ISA, so code generation peculiarities might or might
598.
by inkyoto 4y ago
The compression extension is RISC-V 32-bit. All code has been compiled for 64-bit architectures for a comparison.
599.
by inkyoto 4y ago
> […] aarch64's awful code density […] With all due respect, this is complete nonsense. You keep making this claim, yet have never produced any credible evidence other than a single bogus «ls -l /bin/bash» ages ago for th
600.
by inkyoto 4y ago
I am no stranger to NUMA since SGI days, and AMD EPYC is a ccNUMA. If I read it correctly, 512- and 768-bit wide memory bus is available to access the socketed CPU's local memory only (which is relatively small), and access to the shar

More ›