Hacker News new | past | comments | ask | show | jobs | submit login
Why is there no CR1, and why are control registers such a mess anyway? (2010) (pagetable.com)
99 points by JoshTriplett on Dec 7, 2016 | hide | past | favorite | 15 comments




You have to love comments that spawn links. "Why is that a thing?"


The tl;dr:

  > The i486 added a few more control bits, and some of them
  > went into CR0. But instead of overflowing the new bits
  > into CR1, Intel decided to skip it and open up CR4
  > instead – for unknown reasons.
a.k.a. :shrug:


Spaces in front of your >s make your quote a raw formatted block that's really hard to read on a mobile device. :/


Instead of email-style quotes, just add an asterisk before and after the quoted text. That puts it in italics and makes it obvious that it's quoted material but it will wrap properly on various screen widths.


I wish HN would simply support quoting with `>`. It's a recurring pain. That way it could be made to look good on mobile too...


Strange. It's only 60 characters wide, so it should work fine. But the site fits it into a scrollable box only half the width of the screen.


Yeah, I couldn't believe it when I saw it!


I'm posting from a mobile device and it looks unreadable, I hoped it was just for me because I know it looks fine on desktop…


My suspicion is that some application in the 286 - OS/2 days was found to expect an 'invalid opcode' fault from CR1, so that's why it had to stay reserved.


This reminds me of how INT 0Fh had to stay reserved because of a Pentium Pro errata.


The original 486 did not have CR4. It was added when Intel backported VME and later PSE to later 486 processors.


For those working closer to the metal than I: are these special instructions dispatched to dedicated circuitry, or are they actually microcoded?


> This entry was posted in archeology, trivia, whines on July 2, 2010 by Michael Steil.

So I guess (2010) is appropriate for the title.


It was already old in 2010, nothing has retroactively changed in the text.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: