Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
faragon
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
14 ms
·
121.
▲
by
faragon
8y ago
Dropbear SSH is also shipped into OpenWrt. It works great, including ssh keys, useful for ssh/scp automation.
122.
▲
by
faragon
8y ago
I would love to see projects like MAME and MESS targeting FPGA hardware for near-perfect hardware emulation of classic hardware.
123.
▲
by
faragon
8y ago
Cached: https://web.archive.org/web/20180813200145/http://accu.org/i... Additional material for data-oriented design: https://github.com/dbartolini/data-oriented-design
124.
▲
by
faragon
8y ago
I would love AMD commercials using Judas Priest's "The Ripper" [1] as music for selling those beasts! :-D [1] https://www.youtube.com/watch?v=lriWlHZAy8A
125.
▲
by
faragon
8y ago
Example for C (for structures not using enums nor bitfields, because are compiler-dependant, and avoiding architecture-dependant types like e.g. size_t/ssize_t) : if (islittleendian() && sizeof(mystruct) == REFSIZE_mystruct)
126.
▲
by
faragon
8y ago
Take attention to the "References" section (including references to Linus Torvalds messages in the GCC mail list, some bugs related to this issue, etc.)
127.
▲
by
faragon
8y ago
There are more cases, e.g. the AGP bus (evolution of the original PCI bus for graphics, pre PCI-Express). I don't know if the limitation of the PS3 graphics chip (NVidia RSX) comes because of being derivated from an AGP-based chip or b
128.
▲
by
faragon
8y ago
Yellow Dog Linux 6.1 (and 6.2) for PlayStation 3 (256MB RAM, 256MB of video RAM) had a similar feature [1], being the write fast (GB/s) but the read slow (16 MB/s), because of the graphics bus configuration. It is better than to s
129.
▲
by
faragon
8y ago
In my opinion, Android should focus in quality/stability and UI responsiveness. E.g. it blows my mind that Nokia N900 (2009, Maemo Linux) was, in some cases, way more responsive in the UI than current Android running in hardware 20x fa
130.
▲
by
faragon
8y ago
I hope AMD hits hard the low end, too.
131.
▲
by
faragon
8y ago
I would love to have a laptop with that SoC or similar.
132.
▲
by
faragon
8y ago
Well, maybe westerns not exposed to Asimov's novels directly nor indirectly. Anyway, in such a globalized world, I'm, not sure how right could be that: E.g. Japanese anime is very popular in Europe and America.
133.
▲
by
faragon
8y ago
"Science and Method" (1908, "Science et méthode" -original title in French-) is Poincaré's book the blog post author is speaking about. In my opinion, Poincaré's book is very valuable, and useful for anyone dea
134.
▲
by
faragon
8y ago
"The AMD team found that deadlocks on active interposers basically disappear if you follow a few simple rules when designing on-chip networks" I would like to know how they solved that problem. Is there any public paper or patent
135.
▲
by
faragon
8y ago
Worse than bad: if I recall correctly, there was no C99 support at all until MS VS 2013. Before that you had to compile C as C++ in order to get C99-like features.
136.
▲
by
faragon
8y ago
Could it be just an intentional focus effect?
137.
▲
by
faragon
8y ago
Programmers, and non programmers. In my opinion, companies only scale with trust and respect. Also, it is important for people keeping his self-esteem. Jerks can destroy people without even noticing.
138.
▲
by
faragon
8y ago
Sure. And I love compilers generating very fast code. My point was that there is a ton of code written for x86 on assumptions that are no longer true when compiled with -O3 flags. Fortunately, open source code is less affected because usual
139.
▲
by
faragon
8y ago
Intel CPUs guaranteed correct operation on unaligned accesses. In fact, back in the day, transparent unaligned memory access support, and a strong memory model for SMP, were very strong selling points for Intel vs most RISC vendors. The &qu
140.
▲
by
faragon
8y ago
"was never guaranteed to work by the C standard" It was, on x86 , before of compilers emitting opcodes not supporting unaligned memory accesses, because x86 CPUs guaranteed safe operation on unaligned memory accesses. Don't
141.
▲
by
faragon
8y ago
On x86 CPUs, working with latest compilers in -O3 optimization level is becoming like working with old RISC CPUs without hardware for unaligned load/store: except if you write your code using memcpy/memmove for unaligned load
142.
▲
by
faragon
8y ago
For data compression it uses the LZ4 format [1] (real-time LZ77-like data compressor -without entropy encoding, just string references and literals-, with small blocks so its LUT-based O(1) search is always in the data cache). [1] https:&#
143.
▲
by
faragon
9y ago
Only for SIMD-optimized code. For remaining cases, you can help the compiler so it can generate very fast code (with current OoOE CPUs, the generated code may be suboptimal, but as fast as hand-tuned assembly because of the abundance of ALU
144.
▲
by
faragon
9y ago
Not really. I meant Linus being harsh/impolite sometimes. I like Linus a lot, don't get me wrong :-)
145.
▲
by
faragon
9y ago
Compressing tree data is not trivial. E.g. using per-node heap allocation could take many times the space of the actual data (memory used by the allocator, metainformation, alignment padding, etc.). Using a custom allocator can reduce the m
146.
▲
by
faragon
9y ago
"The W350 tower will be mostly wood, and 10% steel." Wood and steel.
147.
▲
by
faragon
9y ago
Pure gold, indeed. It is a very important reference book (can be found in Amazon both new and used), not only for collision detection, but also for space partition, geometry, code optimization, etc. Also, the author has an amazing blog in t
148.
▲
by
faragon
9y ago
Very interesting, specially the "jpeg-hash" tool, useful for finding quasi-duplicates (different files, but quasi-identical at visual level).
149.
▲
by
faragon
9y ago
For real-time dictionary compression, with infinite-size dictionary (LZ77, using a hash table for O(1) pattern search), you can try: git clone https://github.com/faragon/libsrt cd libsrt make ./enc -ezh <hugefi
150.
▲
by
faragon
9y ago
Sure, specially with some operations, e.g. code requiring "shuffle" operations [1], which use constants for programing byte reordering, having most compilers problems on complex functions, where because of register pressure some &
More ›