Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Annnnnnnnd the hardware was neatly laid out on a graph on the readme. Did you comment before doing ANY reading? That's a feaux pah oh HN.


sort by: page size:

Very nice. I'm going to star all of these. Reminds me my CPU model in 60 lines of code:

https://github.com/wkoszek/cpu60


I'm really enjoying reading this. Ahead of its time.

I really like your RISC CPU in a spreadsheet in Table 1-4. Have you seen others do this since you wrote it?


That’s an impressive piece of work. I would love to know how far this is from the information in the actual internal documentation. It’s very nice to have some excitement about a mainstream CPU architecture again.

Thanks for all the work. That was an amazing read.

I've always wondered how people map chip-die photos into something like this: http://chip-architect.com/news/2007_02_19_Various_Images.htm...

or this: http://chip-architect.com/news/2003_09_21_Detailed_Architect...

I can see how figuring out the cache and the internal buses might be doable, but the rest... Any insights?


Someone should tell the author about the great lshw, it lists full details of the system board (and everything else) without having to go to a GUI display.

  azalp
    description: Desktop Computer
    product: B660M AORUS PRO AX DDR4 (Default string)
    vendor: Gigabyte Technology Co., Ltd.
    version: -CF
    serial: Default string
    width: 64 bits
    capabilities: smbios-3.4.0 dmi-3.4.0 smp vsyscall32
    configuration: boot=normal chassis=desktop family=B660 MB sku=Default string uuid=dotdotdot

People posting those CPU and SSD screens shots rather than, say, some linked data that contributes to make a graph to forums has such a deleterious effect on people's ability to reason. I suppose eventually we'll end up screen scraping the screen shots.

> should be showing on their pages a hardware matrix showing what works and what doesn't.

inb4 What works: You tell me!


It’s compiled from Anandtech benchmarks and archived forum posts. Unfortunately I didn’t write down each source.


> (GitHub - Xilinx/llvm-aie: Fork of LLVM to support AMD AIEngine processors)

Literally the second line of the page I linked to - sometimes I really need to learn to read.



You should probably link to the spec or something in the README so it's easier for people to find.

https://pastebin.com/Rz9k1xMt https://pastebin.com/6bxRYx31

Here are some examples - it's been a bit of a side-obsession for the last few months experimenting with different architectures.

There are so many different ways this could have gone and I've finally zeroed in one an approach that works which is why I'm starting to open up.

There will definitely be a dump in the near future of absolutely everything related to this project.

The ultimate goal was to run it on CPU.


> highly speculative CPU design

Heh. Nice


Thanks. I just found out there's a text abstract one can click to expand ... Snippets:

[...] The cores are our own design; simple 3-address RISCs with read- & write-barriers to support GC, hardware transactional memory, zero-cost high-rez profiling, and some more modest Java-specific tweaks. [...] history with designing our own chips (1st silicon back from the fab had problems like the bits in the odd-numbered registers bleeding into the even-numbered registers)[...]


Wow, now I know where to look the next time I have a hardware project. Nice.

Should point to: http://mail.fsfeurope.org/pipermail/discussion/2016-April/01...

Canonical presentation: REcon 2014 - Intel Management Engine Secrets (Igor Skochinsky) https://www.youtube.com/watch?v=4kCICUPc9_8

Decoding ME firmware in BIOS updates until Skylake (2015): http://io.netgarage.org/me/


Thank you for the details. I guess I had an overly rose-tinted view of the quality of Intel documentation.

Pretty cool stuff. I built a dumber version of this a few years ago that just did differential fuzzing between actual cores from different vendors, but without feedback on microarchitectural state it didn't get very far. Good to see people demonstrating how public descriptions of your parts yield concrete security benefits.

Thanks! I did miss that page. But even though they mention "... calls for the development of software tools to help programming the new architecture...", I'm still unsure as to how programming for such a processor might look like.
next

Legal | privacy