Live data from Hacker News

Viewing profile — newpavlov

newpavlov

HN member
Joined
Wed, Jan 13, 2021, 8:32 AM UTC
HN karma
1,054
Public activity
199 items

About newpavlov

No profile information was provided.

Recent public activity

  1. comment
    Comment #49036950

    Open weight models challenge the "winner takes all" hypothesis, which motivates the astronomical valuations and acts as a justification for trains of cash dumped into AI developmen…

  2. comment
    Comment #48994819

    I wonder if NNs could be trained well enough with 1 bit weights (i.e. 0 and 1) with some layers doing addition, while others substraction (i.e. weight sign would be "hardcoded" int…

  3. comment
    Comment #48831868

    Some people use cryptocurrency miners to heat their homes. It's certainly better than dumb resistive heating, but depending on various conditions it can cost more than installing a…

  4. comment
    Comment #48831734

    Because it's not economical, the required hardware is unlikely to pay for itself during its lifetime. The gradient is too small (~50C), which means low Carnot efficiency. Additiona…

  5. comment
    Comment #48495606

    >There is no "objective" foundation to music. Well, there is a number of "objective" factors which play a significant role. For example, see: https://www.youtube.com/watch?v=tCsl6Z…

  6. comment
    Comment #48180771

    >Its capabilities all the way down. IIUC one problem with such layering of capability processing is that each passed layer results in a context switch (i.e. switch of memory mappin…

  7. comment
    Comment #47778662

    No, it's not. Launch windows [0] are about relative position of orbital bodies which enable use of more efficient transfer orbits. [0]: https://en.wikipedia.org/wiki/Launch_window

  8. comment
    Comment #47778111

    >Are we going to run out of space? In a certain sense, we do. Pumping thousands satellites to LEO increases probability of triggering the Kessler syndrome. Luckily, LEO orbits are …

  9. comment
    Comment #47628869

    For Rust we have Loom [0], but do not expect for it to work on your whole application. [0]: https://github.com/tokio-rs/loom

  10. comment
    Comment #47626844

    Isn't it just a lawmakers' version of diff? :) You just can't conveniently apply it automatically to compile the resulting text. >Why the hell you not just rewrite the old law and …

  11. comment
    Comment #47591966

    >it requires creating logical qubits with error rates that we are only now seeing companies report And yet 21 was not factored on a real hardware. >There is linear engineering prog…

  12. comment
    Comment #47591757

    >The underlying scaling needed to go to 32 bit requires only linear progress to get to 256 Nope. Firstly, for RSA you need to scale from 32 to 4096. Secondly, Shor requires N^2*log…

  13. comment
    Comment #47591647

    Dup? https://news.ycombinator.com/item?id=47582418

  14. comment
    Comment #47583719

    Have they factored 21 yet? [0] IMO most of us can ignore such pieces until a practical factorization of arbitrary 32 bit integers is demonstrated on a QC. And even after this "easy…

  15. comment
    Comment #47336880

    >1 might be ok but introduces a bunch of opcode space waste. I wouldn't call it "waste". Moreover, it's fine for misaligned instructions to use a wider encoding or be less rich tha…

  16. comment
    Comment #47335752

    I am not saying that RISC-V should mandate performance. If anything, we wouldn't had the problem with Zicclsm if they did not bother with the stupid performance note. I would be fi…

  17. comment
    Comment #47333928

    >So just use misaligned loads if Zicclsm is supported. LLVM and GCC developers clearly disagree with you. In other words, re-iterating the previously raised point: Zicclsm is effec…

  18. comment
    Comment #47333779

    >Multiply and divide And where it actually mattered they did not introduce a separate extension. Integer division is significantly more complex than multiplication, so it may make …

  19. comment
    Comment #47333725

    >As for `seed`, if you're running on a microcontroller you can just look up the data sheet to see if it's seed entropy is sufficient. It's a terrible attitude to have towards progr…

  20. comment
    Comment #47330046

    >Misaligned loads and stores are Zicclsm Nope. See https://github.com/llvm/llvm-project/issues/110454 which was linked in the first issue. The spec authors have managed to made a m…

  21. comment
    Comment #47328930

    In some cases RISC-V ISA spec is definitely the one to blame: 1) https://github.com/llvm/llvm-project/issues/150263 2) https://github.com/llvm/llvm-project/issues/141488 Another ex…

  22. story
  23. comment
    Comment #46975023

    Compilers also like to unnecessarily copy data to stack: https://github.com/llvm/llvm-project/issues/53348 Which can be particularly annoying in cryptographic code where you want t…

  24. comment
    Comment #46677286

    >The obvious next step is to do all the math in client-side code and just have the user enter the secret https://en.wikipedia.org/wiki/Password-authenticated_key_agr...

  25. comment
    Comment #46368175

    IIRC at least one of the `restrict` bugs found by Rust was reproduced on both LLVM and GCC.