Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

I'm unable to find any confirmation of that supposed $120M investment in Bluesky.

Uncategorized
6 3 1

Gli ultimi otto messaggi ricevuti dalla Federazione
  • How the Intel 8087 FPU Knows Which Instructions to Execute

    An interesting detail about the Intel 8087 floating point processor (FPU) is that it’s a co-processor that shares a bus with the 8086 or 8088 CPU and system memory, which means that somehow both the CPU and FPU need to know which instructions are intended for the FPU. Key to this are eight so-called ESCAPE opcodes that are assigned to the co-processor, as explained in a recent article by [Ken Shirriff].

    The 8087 thus waits to see whether it sees these opcodes, but since it doesn’t have access to the CPU’s registers, sharing data has to occur via system memory. The address for this is calculated by the CPU and read from by the CPU, with this address registered by the FPU and stores for later use in its BIU register. From there the instruction can be fully decoded and executed.

    This decoding is mostly done by the microcode engine, with conditional instructions like cos featuring circuitry that sprawls all over the IC. Explained in the article is how the microcode engine even knows how to begin this decoding process, considering the complexity of these instructions. The biggest limitation at the time was that even a 2 kB ROM was already quite large, which resulted in the 8087 using only 22 microcode entry points, using a combination of logic gates and PLAs to fully implement the entire ROM.

    Only some instructions are directly implemented in hardware at the bus interface (BIU), which means that a lot depends on this microcode engine and the ROM for things to work half-way efficiently. This need to solve problems like e.g. fetching constants resulted in a similarly complex-but-transistor-saving approach for such cases.

    Even if the 8087 architecture is convoluted and the ISA not well-regarded today, you absolutely have to respect the sheer engineering skills and out-of-the-box thinking of the 8087 project’s engineers.

    hackaday.com/2026/02/21/how-th…

    read more

  • @danjones000 @Matt_Noyes there are numbers in the world and you can use them to compare things to other things.

    read more

  • @danjones000 @Matt_Noyes read the rest of the thread. Adding in training gets us to about 0.0065kg CO2eq, although it's not clear if they count that in the original estimate.

    read more

  • @thisismissem would be good to know which URLs fail to resolve. It could be that NodeBB returned a 503 and that would lead to a failure in resolution. Just let me know next time it happens 😊

    As for an intro banner, that's a neat idea. @baris@community.nodebb.org actually added something at the bottom of a topic, but it does make sense to add some AP specific text in the too.

    read more

  • Hacktivists tried to find a workaround to Discord’s age-verification software, Persona. Instead, they found its frontend exposed to the open internet, and that was just the beginning.

    https://www.therage.co/persona-age-verification/

    read more

  • @mcc I so want this too. Moreover, I want some kind of standard/standardized compact/agreement/declaration/license that F/OSS projects individually could reference to declare that they agree with and enforce this stance: no "AI" contributions whatsoever. Have not yet found such a thing.

    I agree that the distro level is the right place for this, but there's an argument to be made that it should go all the way down.

    read more

  • One thing for sure, I’ve got a fire under my butt to get out of 1password pretty quick.

    read more

  • @johnlehet Yes; I am attempting to describe the product sold as "AI code assistants" without using the word "AI". It did not occur to me that "code" was ambiguous/a pun when I made the post.

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    2 Views
    How the Intel 8087 FPU Knows Which Instructions to ExecuteAn interesting detail about the Intel 8087 floating point processor (FPU) is that it’s a co-processor that shares a bus with the 8086 or 8088 CPU and system memory, which means that somehow both the CPU and FPU need to know which instructions are intended for the FPU. Key to this are eight so-called ESCAPE opcodes that are assigned to the co-processor, as explained in a recent article by [Ken Shirriff].The 8087 thus waits to see whether it sees these opcodes, but since it doesn’t have access to the CPU’s registers, sharing data has to occur via system memory. The address for this is calculated by the CPU and read from by the CPU, with this address registered by the FPU and stores for later use in its BIU register. From there the instruction can be fully decoded and executed.This decoding is mostly done by the microcode engine, with conditional instructions like cos featuring circuitry that sprawls all over the IC. Explained in the article is how the microcode engine even knows how to begin this decoding process, considering the complexity of these instructions. The biggest limitation at the time was that even a 2 kB ROM was already quite large, which resulted in the 8087 using only 22 microcode entry points, using a combination of logic gates and PLAs to fully implement the entire ROM.Only some instructions are directly implemented in hardware at the bus interface (BIU), which means that a lot depends on this microcode engine and the ROM for things to work half-way efficiently. This need to solve problems like e.g. fetching constants resulted in a similarly complex-but-transistor-saving approach for such cases.Even if the 8087 architecture is convoluted and the ISA not well-regarded today, you absolutely have to respect the sheer engineering skills and out-of-the-box thinking of the 8087 project’s engineers.hackaday.com/2026/02/21/how-th…
  • 0 Votes
    1 Posts
    0 Views
    Didn't have quite enough rice, so I topped up the cup with lentils, and added a little extra water. Should be fine, right? More protein and fiber can't be bad.
  • I want this but as a Linux distribution.

    Uncategorized
    55
    0 Votes
    55 Posts
    1 Views
    @mcc I so want this too. Moreover, I want some kind of standard/standardized compact/agreement/declaration/license that F/OSS projects individually could reference to declare that they agree with and enforce this stance: no "AI" contributions whatsoever. Have not yet found such a thing.I agree that the distro level is the right place for this, but there's an argument to be made that it should go all the way down.
  • 0 Votes
    13 Posts
    0 Views
    @futurebird No lies detected!!