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
  1. Home
  2. Categories
  3. Uncategorized
  4. Since the topic came up in the whole "I run models locally so it's all fine" conversation:

Since the topic came up in the whole "I run models locally so it's all fine" conversation:

Uncategorized
12 10 0
Log in to reply

Feed RSS
Since the topic came up in the whole "I run models locally so it's all fine" conversation:

Gli ultimi otto messaggi ricevuti dalla Federazione
@pierobosio@soc.bosio.info
Post suggeriti
  • 123podcast@castopod.cgubi.synology.meundefined

    Conversazione con Maurizio Acerbo nell'anniversario del "Manifesto" di Marx ed Engels

    Uncategorized
    1
    0 Votes
    1 Posts
    2 Views
    123podcast@castopod.cgubi.synology.meundefined
    Conversazione con Maurizio Acerbo nell'anniversario del "Manifesto" di Marx ed Engels.S01E21: 60 minuti di comunismo, cultura, storia, politica e società, in una conversazione con Maurizio Acerbo, segretario di @rifondazione Comunista. In allegato libri di Marx, Engels, Gramsci, Burroughs, Hobsbawm. Colonna sonora a cura di Bob Dylan, Simple Minds, Arturo Toscanini. Buon ascolto, buone letture e buona resistenza.
  • cybersecurity@poliverso.orgundefined

    How the Intel 8087 FPU Knows Which Instructions to Execute

    Uncategorized
    1
    1
    0 Votes
    1 Posts
    3 Views
    cybersecurity@poliverso.orgundefined
    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…
  • markhurst@mastodon.socialundefined

    Now THAT's a headline.

    Uncategorized edtech education
    22
    0 Votes
    22 Posts
    9 Views
    pizzademon@mastodon.onlineundefined
    @markhurst imagine being the kid picked for this picture
  • naturzukunft2026@mastodon.socialundefined

    Have I already mentioned that the “Show thread” request is slowly driving me crazy?

    Uncategorized c2s activitypub fep7888
    2
    0 Votes
    2 Posts
    0 Views
    julian@activitypub.spaceundefined
    @naturzukunft2026@mastodon.social what's a "show thread" request?