Live data from Hacker News

Viewing profile — _chris_

_chris_

HN member
Joined
Wed, Aug 06, 2014, 8:26 PM UTC
HN karma
687
Public activity
217 items

About _chris_

RISC-V and Chisel user.

riscv.org chisel.eecs.berkeley.edu https://github.com/ucb-bar/riscv-sodor https://github.com/ucb-bar/riscv-boom

Recent public activity

  1. comment
    Comment #45244018

    Longer time horizon -- mortage inflates away. In the short-term, only need to beat the property tax bill, especially if the interest rate is <3% and the property is increasing in v…

  2. comment
    Comment #44956728

    A BPU needs to predict 3 things: - 1) Is there a branch here? - 2) If so, is it taken? - 3) If so, where to? If a conditional branch is never taken, then it's effectively a NOP, an…

  3. comment
    Comment #44956513

    > A lot of the time this is a hint to the compiler on what the expected paths are so it can keep those paths linear. IIRC, this mainly helps instruction cache locality. The real va…

  4. comment
    Comment #44956481

    > The thing holding back VLIW was compilers were too dumb That’s not really the problem. The real issue is that VLIW requires branches to be strongly biased, statically, so a compi…

  5. comment
    Comment #43094774

    Wouldn’t a smart tv do something ... smarter than just using the default dns given to it by the network? I’m not up to speed on this stuff but I thought pihole only blocked the sim…

  6. comment
    Comment #42966615

    It’s not that hard to debug— your signal names and register names all carry through. Sure, lots of temp wires get generated but that’s never where your bug is.

  7. comment
    Comment #41451290

    > allow to select the purchase price within the last 2 years I don't think that's true. My reading of that is "you lock in the price on your start date and can keep that for the ne…

  8. comment
    Comment #39115765

    > I’d be interested in understanding why the compilers never panned out but have never seen a good writeup on that. Or why people thought the compilers would be able to succeed in …

  9. comment
    Comment #39046786

    > L1i matters, people! RISC-V consistently wins on L1i footprint. The complaining is about number of dynamic instructions ("path length"), which can hit you if you don't fuse. Of c…

  10. comment
  11. comment
  12. comment
    Comment #38018678

    > > Cascade discovered 4 bugs in BOOM and CVA6 that produce wrong output val- ues regardless of the microarchitectural state > These are unacceptable bugs, showing a lack of archit…

  13. comment
    Comment #38018637

    Looks like from Appendix D that only 2 bugs were found in BOOM: > 1. Inaccurate instruction count when minstret is written by software I don't know what that means, but having mins…

  14. comment
  15. comment
    Comment #37044899

    If you want to do some further archeology, check out the SMIPS ISA, which I believe dates back to 2005 (which itself gradually evolved from the T0/Scale/6.371 MIPS ISAs; and the ea…

  16. comment
    Comment #37044165

    I also get a permission error: but I think this ( https://inst.eecs.berkeley.edu/~cs250/fa10/handouts/lab2-ris... ) is the same file, and functionally the same as the fa11 version?…

  17. comment
    Comment #37040625

    To add to this, Andrew et. al. at Berkeley built SPARC cores, so they were well aware of what it took to implement hardware to run SPARC software. I believe some of the really anno…

  18. comment
    Comment #37040572

    I believe early on there was a change to a pre-AUIPC instruction due to potential infringement fears (for PC-relative indexing); but everything else was understood to be following …

  19. comment
    Comment #36853545

    And adds non-destructive instructions. > "In addition, legacy integer instructions now can also use EVEX to encode a dedicated destination register operand – turning them into thre…

  20. comment
    Comment #31526188

    > their clean orthogonal instruction encoding is so inefficient (e.g. it wastes a lot of instruction cache) Perhaps, although ARMv8 is fixed 4 bytes and x86-64 averages more than 4…

  21. comment
    Comment #30180567

    Custom opcodes have a protected spot in the opcode map; but there's nothing that prevents two different CPUs from using the same custom opcode pattern to mean two different instruc…

  22. comment
    Comment #29420516

    Very different. RISC-V's vectors (RVV) are "variable length", so the programmer can request a length and the machine tells you what it can give you. Different machine versions can …

  23. comment
    Comment #28768313

    > They said "5 stage", which sounds to me like no out-of-order fancy stuff of the sort we've been used to. That's inefficient for an FPGA softcore; wires are too expensive, CAMs ar…

  24. comment
    Comment #27544911

    > I wonder if we're ever going to see a 8wide decoder RISC-V. Considering there are 6-wide x86 cores on the market, I wouldn't be too concerned about RISC-V going wide. The instruc…

  25. comment
    Comment #27258892

    Lying all the time has consequences.