Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.math > #641533 > unrolled thread

Re: parallel random-access machine (parallel RAM or PRAM (Was: What is analog computing nowadays?)

Back to article view | Back to sci.math

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: parallel random-access machine (parallel RAM or PRAM (Was: What is analog computing nowadays?) Pascual Sokolsky <aoa@ssppsc.pl> - 2025-12-01 19:58 +0000
    Re: parallel random-access machine (parallel RAM or PRAM (Was: What is analog computing nowadays?) Mild Shock <janburse@fastmail.fm> - 2025-12-01 21:17 +0100
      Re: parallel random-access machine (parallel RAM or PRAM (Was: What is analog computing nowadays?) Blending Molostvov <noo@biiooe.ru> - 2025-12-01 20:44 +0000
        Algorithm introduced in Hogwild! SGD (Niu et al., 2011) (Re: parallel random-access machine) Mild Shock <janburse@fastmail.fm> - 2025-12-01 22:06 +0100
          Linux kernel's RCU-protected hash tables (Re: Algorithm introduced in Hogwild! SGD (Niu et al., 2011)) Mild Shock <janburse@fastmail.fm> - 2025-12-01 22:26 +0100
            String interning is HashSet and not HashMap (Was: Linux kernel's RCU-protected hash tables) Mild Shock <janburse@fastmail.fm> - 2025-12-01 22:40 +0100
          Re: Algorithm introduced in Hogwild! SGD (Niu et al., 2011) (Re: parallel random-access machine) Bosephis Otlesnov <ooiv@th.ru> - 2025-12-01 21:42 +0000
            POINT OF VIEW OF AN ALGORITHM (Re: Algorithm introduced in Hogwild! SGD (Niu et al., 2011)) (Re: parallel random-access machine) Mild Shock <janburse@fastmail.fm> - 2025-12-01 23:12 +0100
              Introduction to AMBA® 4 ACE™ (2011) (Was: POINT OF VIEW OF AN ALGORITHM) Mild Shock <janburse@fastmail.fm> - 2025-12-01 23:37 +0100
                Sputnik Schock: Academia is Disposable [I. J. Good Ultraintelligence] (Was: Introduction to AMBA® 4 ACE™ (2011)) Mild Shock <janburse@fastmail.fm> - 2025-12-01 23:53 +0100
                Re: Introduction to AMBA® 4 ACE™ (2011) (Was: POINT OF VIEW OF AN ALGORITHM) Josbanne Balagula <ajbn@oll.ru> - 2025-12-01 23:06 +0000
                  Re: Introduction to AMBA® 4 ACE™ (2011) (Was: POINT OF VIEW OF AN ALGORITHM) Mild Shock <janburse@fastmail.fm> - 2025-12-02 00:08 +0100

#641533 — Re: parallel random-access machine (parallel RAM or PRAM (Was: What is analog computing nowadays?)

Mild Shock wrote:

> But in principle the architecture is rather:
> 
> parallel random-access machine (parallel RAM or PRAM) is a shared-memory
> abstract machine. https://en.wikipedia.org/wiki/Parallel_RAM
> 
> The above class of machines is not widely know.
> But PRAM has been also studied, already in the 80's.

parallel read of shared memory is only allowed to cia and the chinese 
governoment; must be somenthing you dont know 

[toc] | [next] | [standalone]

#641534

What are you, a 5 year old moron?

Pascual Sokolsky schrieb:
> Mild Shock wrote:
> 
>> But in principle the architecture is rather:
>>
>> parallel random-access machine (parallel RAM or PRAM) is a shared-memory
>> abstract machine. https://en.wikipedia.org/wiki/Parallel_RAM
>>
>> The above class of machines is not widely know.
>> But PRAM has been also studied, already in the 80's.
> 
> parallel read of shared memory is only allowed to cia and the chinese
> governoment; must be somenthing you dont know
> 

[toc] | [prev] | [next] | [standalone]

#641535

Mild Shock wrote:

> What are you, a 5 year old moron?
> 
> Pascual Sokolsky schrieb:
>> Mild Shock wrote:
>> 
>>> But in principle the architecture is rather:
>>>
>>> parallel random-access machine (parallel RAM or PRAM) is a
>>> shared-memory abstract machine.
>>> https://en.wikipedia.org/wiki/Parallel_RAM
>>>
>>> The above class of machines is not widely know.
>>> But PRAM has been also studied, already in the 80's.
>> 
>> parallel read of shared memory is only allowed to cia and the chinese
>> governoment; must be somenthing you dont know

from shared memory you only read and write sequential, me frendo,
driven by semaphores, atomic instructions and so on. You are not that
fucking stupid to write parallel to a cell, are you

[toc] | [prev] | [next] | [standalone]

#641536 — Algorithm introduced in Hogwild! SGD (Niu et al., 2011) (Re: parallel random-access machine)

Hi,

What are you, a 5 year old moron?

There are millions of algorithm that use volatile
variables. Just look at the Java code base.

But I was not refering to multi-threading, I
was refering to PRAM for matrix operations.

See for example here:

Hogwild!: A Lock-Free Approach to
Parallelizing Stochastic Gradient Descent
https://arxiv.org/pdf/1106.5730

Fuck off moron.

Bye

Blending Molostvov schrieb:
> Mild Shock wrote:
> 
>> What are you, a 5 year old moron?
>>
>> Pascual Sokolsky schrieb:
>>> Mild Shock wrote:
>>>
>>>> But in principle the architecture is rather:
>>>>
>>>> parallel random-access machine (parallel RAM or PRAM) is a
>>>> shared-memory abstract machine.
>>>> https://en.wikipedia.org/wiki/Parallel_RAM
>>>>
>>>> The above class of machines is not widely know.
>>>> But PRAM has been also studied, already in the 80's.
>>>
>>> parallel read of shared memory is only allowed to cia and the chinese
>>> governoment; must be somenthing you dont know
> 
> from shared memory you only read and write sequential, me frendo,
> driven by semaphores, atomic instructions and so on. You are not that
> fucking stupid to write parallel to a cell, are you
> 

[toc] | [prev] | [next] | [standalone]

#641537 — Linux kernel's RCU-protected hash tables (Re: Algorithm introduced in Hogwild! SGD (Niu et al., 2011))

Hi,

An example of a lock free datastructure, that
even doesn't use CAS, is for example:

Read-Copy-Update (RCU) Based Hash Tables
These use only memory barriers/fences and atomic pointer writes:
- Basic approach: Readers access the table without locks,
   writers create new versions
- Memory reclamation: Uses RCU grace periods instead of CAS
- Example: Linux kernel's RCU-protected hash tables
- Operations: Only requires atomic loads/stores and memory barriers

For Prolog systems there are also various
approaches arround, if one aims at the multi-threading
model for dynamic databass or atom tables.

I think this multi-threading model should be
abadoned, in favor of things that can be speed
up by a AI accelerator. Dogelog Player has abandoned

multi-threading all together. But for example
SWI-Prolog has heavily focused on lock free
data structures already like 10 years ago,

and it seems YAP can still not keep up with
SWI-Prolog. See for example here:

Yet Another Lock-Free Atom Table Design
for Scalable Symbol Management in Prolog
https://link.springer.com/article/10.1007/s10766-024-00766-z

But in my opinion, in the light of the AI Boom,
this is all amplified nonsense.

Bye

Mild Shock schrieb:
> Hi,
> 
> What are you, a 5 year old moron?
> 
> There are millions of algorithm that use volatile
> variables. Just look at the Java code base.
> 
> But I was not refering to multi-threading, I
> was refering to PRAM for matrix operations.
> 
> See for example here:
> 
> Hogwild!: A Lock-Free Approach to
> Parallelizing Stochastic Gradient Descent
> https://arxiv.org/pdf/1106.5730
> 
> Fuck off moron.
> 
> Bye
> 
> Blending Molostvov schrieb:
>> Mild Shock wrote:
>>
>>> What are you, a 5 year old moron?
>>>
>>> Pascual Sokolsky schrieb:
>>>> Mild Shock wrote:
>>>>
>>>>> But in principle the architecture is rather:
>>>>>
>>>>> parallel random-access machine (parallel RAM or PRAM) is a
>>>>> shared-memory abstract machine.
>>>>> https://en.wikipedia.org/wiki/Parallel_RAM
>>>>>
>>>>> The above class of machines is not widely know.
>>>>> But PRAM has been also studied, already in the 80's.
>>>>
>>>> parallel read of shared memory is only allowed to cia and the chinese
>>>> governoment; must be somenthing you dont know
>>
>> from shared memory you only read and write sequential, me frendo,
>> driven by semaphores, atomic instructions and so on. You are not that
>> fucking stupid to write parallel to a cell, are you
>>
> 

[toc] | [prev] | [next] | [standalone]

#641539 — String interning is HashSet and not HashMap (Was: Linux kernel's RCU-protected hash tables)

Hi,

The Linux kernel's RCU-protected hash tables
is still not free of problems. Multiple writers
might still need extra work.

String interning with a HashSet (no values, just keys)
is actually easier to make lock-free without full
CAS because you're only concerned with existence,

not updates.

Bye

P.S.: I am not affected by this amplified nonsense.
Dogelog Player has even no atom table. And since it
is single threaded, the HashMap for predicate lookup

is totally lock free. It is single threaded and it
has cooperative multithreading. Internally it uses
async/await from JavaScript for example, which is

a cooperative multthreading approach, but from the
outside it provides tasks and sleep and stuff.
Recently demonstrated a little Strudel style music coding:

Strudel Coding in Dogelog Player
https://medium.com/2989/bbb9c78fcd67

In basically declared multi-threading dead, before
AI accelerators were there. I had more some worker
things in mind, with more thorough siloing and isolation.

But now that we have AI accelerators, the decision
to abandon multithreadinhg looks even more splendid.

Mild Shock schrieb:
> Hi,
> 
> An example of a lock free datastructure, that
> even doesn't use CAS, is for example:
> 
> Read-Copy-Update (RCU) Based Hash Tables
> These use only memory barriers/fences and atomic pointer writes:
> - Basic approach: Readers access the table without locks,
>    writers create new versions
> - Memory reclamation: Uses RCU grace periods instead of CAS
> - Example: Linux kernel's RCU-protected hash tables
> - Operations: Only requires atomic loads/stores and memory barriers
> 
> For Prolog systems there are also various
> approaches arround, if one aims at the multi-threading
> model for dynamic databass or atom tables.
> 
> I think this multi-threading model should be
> abadoned, in favor of things that can be speed
> up by a AI accelerator. Dogelog Player has abandoned
> 
> multi-threading all together. But for example
> SWI-Prolog has heavily focused on lock free
> data structures already like 10 years ago,
> 
> and it seems YAP can still not keep up with
> SWI-Prolog. See for example here:
> 
> Yet Another Lock-Free Atom Table Design
> for Scalable Symbol Management in Prolog
> https://link.springer.com/article/10.1007/s10766-024-00766-z
> 
> But in my opinion, in the light of the AI Boom,
> this is all amplified nonsense.
> 
> Bye
> 
> Mild Shock schrieb:
>> Hi,
>>
>> What are you, a 5 year old moron?
>>
>> There are millions of algorithm that use volatile
>> variables. Just look at the Java code base.
>>
>> But I was not refering to multi-threading, I
>> was refering to PRAM for matrix operations.
>>
>> See for example here:
>>
>> Hogwild!: A Lock-Free Approach to
>> Parallelizing Stochastic Gradient Descent
>> https://arxiv.org/pdf/1106.5730
>>
>> Fuck off moron.
>>
>> Bye
>>
>> Blending Molostvov schrieb:
>>> Mild Shock wrote:
>>>
>>>> What are you, a 5 year old moron?
>>>>
>>>> Pascual Sokolsky schrieb:
>>>>> Mild Shock wrote:
>>>>>
>>>>>> But in principle the architecture is rather:
>>>>>>
>>>>>> parallel random-access machine (parallel RAM or PRAM) is a
>>>>>> shared-memory abstract machine.
>>>>>> https://en.wikipedia.org/wiki/Parallel_RAM
>>>>>>
>>>>>> The above class of machines is not widely know.
>>>>>> But PRAM has been also studied, already in the 80's.
>>>>>
>>>>> parallel read of shared memory is only allowed to cia and the chinese
>>>>> governoment; must be somenthing you dont know
>>>
>>> from shared memory you only read and write sequential, me frendo,
>>> driven by semaphores, atomic instructions and so on. You are not that
>>> fucking stupid to write parallel to a cell, are you
>>>
>>
> 

[toc] | [prev] | [next] | [standalone]

#641540 — Re: Algorithm introduced in Hogwild! SGD (Niu et al., 2011) (Re: parallel random-access machine)

Mild Shock wrote:

> What are you, a 5 year old moron?
> 
> There are millions of algorithm that use volatile variables. Just look
> at the Java code base.
> 
> But I was not refering to multi-threading, I was refering to PRAM for
> matrix operations.

i thought you said you wanna read and write parallel to RAM, aka PRAM, let 
me see.. zum zum zum, yeah, you said that. Take a lock at timing 
requirements for a read/write cycle, deadlines etc, shared memory or not, 
fucking idiot.

[toc] | [prev] | [next] | [standalone]

#641541 — POINT OF VIEW OF AN ALGORITHM (Re: Algorithm introduced in Hogwild! SGD (Niu et al., 2011)) (Re: parallel random-access machine)

Hi,

I am not saying anything. Thats the definition of PRAM.
Whats wrong with you, are you a 5 year old moron.
I am only citing a theoretical computer science model:

- Concurrent read concurrent write (CRCW)—multiple
processors can read and write. A CRCW PRAM is sometimes
called a concurrent random-access machine.
https://en.wikipedia.org/wiki/Parallel_RAM

Technically with multi-channel memory nowadays, it
doesn't need locks on the hardware level, only tiny
serialization, could even happen outside of the CPU.

So if you drop some barrier requirements, you could
really have the chaos of a PRAM, for worse or
for better. I think you need to accept that,

even if its to big to fit in your tiny squirrel brain.

Bye

P.S.: "effectively CREW, since only one write per address at
a time", it will just block the other cores? Short answer:
Yes — if two cores try to write the same address, one

of them is forced to stall (block) until the other completes.
In real hardware, the effect can mimic CRCW behavior over
a short time window, even though it’s not truly simultaneous.

this blocking usually happens in the cache-coherence
system, not at DRAM. Modern CPUs use MESI/MOESI. It happens
over a small interval [t₁, t₂] dictated by cache coherence.

 From the POINT OF VIEW OF AN ALGORITHM, it’s “CRCW enough.”


Bosephis Otlesnov schrieb:
> Mild Shock wrote:
> 
>> What are you, a 5 year old moron?
>>
>> There are millions of algorithm that use volatile variables. Just look
>> at the Java code base.
>>
>> But I was not refering to multi-threading, I was refering to PRAM for
>> matrix operations.
> 
> i thought you said you wanna read and write parallel to RAM, aka PRAM, let
> me see.. zum zum zum, yeah, you said that. Take a lock at timing
> requirements for a read/write cycle, deadlines etc, shared memory or not,
> fucking idiot.
> 

[toc] | [prev] | [next] | [standalone]

#641542 — Introduction to AMBA® 4 ACE™ (2011) (Was: POINT OF VIEW OF AN ALGORITHM)

Hi,

Come on squirrel brain, that we practically have
PRAM on multi-core CPUs, is an old hat. ARM kept
up with MESI/MOESI in 2011:

https://developer.arm.com/-/media/Arm%20Developer%20Community/PDF/CacheCoherencyWhitepaper_6June2011.pdf

What are you squirrel brain, some russion developer
controlling a drone from within EMACS ? Meanwhile
ARM and Intel and Snapdragon etc.. have developed

much more marvels than only this simple PRAM.
The excitement on the side of ARM is quite big,
that they got into the boat of OpenAI:

OpenAI co-founder on new deal with AMD
https://www.youtube.com/watch?v=WuXCNpbO9hI

Bye

P.S.: Because of contention, you should of course
only use volatile variables carefully. It might
not scale well to 1000 cores.

There are also algorithms around to lift the
pressure when there is a large amount of cores.
Even Doug Lea has already put a few utilities in

java.concurrent.* for certain problems with large
number of cores, kind of easter eggs in java.concurrent.*.
But I am not sure whether Doug Lea is involved in

additions for AI accelerators. But he is in the
Program Committee of:

Parallel programming for emerging hardware, including
AI accelerators, processor-in-memory, programmable logic,
non-volatile memory technologies, and quantum computers
https://ppopp26.sigplan.org/track/PPoPP-2026-papers

It could be that the data flow compiler, things sketched
by OpenXLA already work well enough.

Mild Shock schrieb:
> Hi,
> 
> I am not saying anything. Thats the definition of PRAM.
> Whats wrong with you, are you a 5 year old moron.
> I am only citing a theoretical computer science model:
> 
> - Concurrent read concurrent write (CRCW)—multiple
> processors can read and write. A CRCW PRAM is sometimes
> called a concurrent random-access machine.
> https://en.wikipedia.org/wiki/Parallel_RAM
> 
> Technically with multi-channel memory nowadays, it
> doesn't need locks on the hardware level, only tiny
> serialization, could even happen outside of the CPU.
> 
> So if you drop some barrier requirements, you could
> really have the chaos of a PRAM, for worse or
> for better. I think you need to accept that,
> 
> even if its to big to fit in your tiny squirrel brain.
> 
> Bye
> 
> P.S.: "effectively CREW, since only one write per address at
> a time", it will just block the other cores? Short answer:
> Yes — if two cores try to write the same address, one
> 
> of them is forced to stall (block) until the other completes.
> In real hardware, the effect can mimic CRCW behavior over
> a short time window, even though it’s not truly simultaneous.
> 
> this blocking usually happens in the cache-coherence
> system, not at DRAM. Modern CPUs use MESI/MOESI. It happens
> over a small interval [t₁, t₂] dictated by cache coherence.
> 
>  From the POINT OF VIEW OF AN ALGORITHM, it’s “CRCW enough.”
> 
> 
> Bosephis Otlesnov schrieb:
>> Mild Shock wrote:
>>
>>> What are you, a 5 year old moron?
>>>
>>> There are millions of algorithm that use volatile variables. Just look
>>> at the Java code base.
>>>
>>> But I was not refering to multi-threading, I was refering to PRAM for
>>> matrix operations.
>>
>> i thought you said you wanna read and write parallel to RAM, aka PRAM, 
>> let
>> me see.. zum zum zum, yeah, you said that. Take a lock at timing
>> requirements for a read/write cycle, deadlines etc, shared memory or not,
>> fucking idiot.
>>
> 

[toc] | [prev] | [next] | [standalone]

#641544 — Sputnik Schock: Academia is Disposable [I. J. Good Ultraintelligence] (Was: Introduction to AMBA® 4 ACE™ (2011))

Hi,

Looking at how they phrase it:

"symposium focuses on improving the programming
productivity and performance engineering of all
concurrent and parallel systems—multicore, multi-
threaded, heterogeneous, clustered, and distributed
systems, grids, accelerators such as ASICs, GPUs,
FPGAs, data centers, clouds, large scale machines,
and quantum computers. PPoPP is also interested in
new and emerging parallel workloads and applications,
such as artificial intelligence and large-scale
scientific/enterprise workloads."
https://ppopp26.sigplan.org/track/PPoPP-2026-papers

It could be also that academia was overrun by the AI boom.
Is lost in the nowhere. That the techno lords have
created realities turning the academia into savages.

No wonder there is a call for automated AI researchers,
and automated AI engineers, by the AI industry itself.
And which might be the outcome of the current manhatten

project, also known as genesis mission. So that the AI
can be programmed by AI, AI which is more knowledgable
than tiny accademics. We are maybe heading towards a

first Ultraintelligence, that will then shape subsequent
Ultraintelligences. As described by I. J. Good:

"Let an ultraintelligent machine be defined as a machine
that can far surpass all the intellectual activities of
any man however clever. Since the design of machines is
one of these intellectual activities, an ultraintelligent
machine could design even better machines; there would
then unquestionably be an 'intelligence explosion,' and
the intelligence of man would be left far behind...
Thus the first ultraintelligent machine is the last
invention that man need ever make, provided that the
machine is docile enough to tell us how to keep it under
control. It is curious that this point is made so
seldom outside of science fiction. It is sometimes
worthwhile to take science fiction seriously."
https://exhibits.stanford.edu/feigenbaum/catalog/gz727rg3869

Bye

Mild Shock schrieb:
> Hi,
> 
> Come on squirrel brain, that we practically have
> PRAM on multi-core CPUs, is an old hat. ARM kept
> up with MESI/MOESI in 2011:
> 
> https://developer.arm.com/-/media/Arm%20Developer%20Community/PDF/CacheCoherencyWhitepaper_6June2011.pdf 
> 
> 
> What are you squirrel brain, some russion developer
> controlling a drone from within EMACS ? Meanwhile
> ARM and Intel and Snapdragon etc.. have developed
> 
> much more marvels than only this simple PRAM.
> The excitement on the side of ARM is quite big,
> that they got into the boat of OpenAI:
> 
> OpenAI co-founder on new deal with AMD
> https://www.youtube.com/watch?v=WuXCNpbO9hI
> 
> Bye
> 
> P.S.: Because of contention, you should of course
> only use volatile variables carefully. It might
> not scale well to 1000 cores.
> 
> There are also algorithms around to lift the
> pressure when there is a large amount of cores.
> Even Doug Lea has already put a few utilities in
> 
> java.concurrent.* for certain problems with large
> number of cores, kind of easter eggs in java.concurrent.*.
> But I am not sure whether Doug Lea is involved in
> 
> additions for AI accelerators. But he is in the
> Program Committee of:
> 
> Parallel programming for emerging hardware, including
> AI accelerators, processor-in-memory, programmable logic,
> non-volatile memory technologies, and quantum computers
> https://ppopp26.sigplan.org/track/PPoPP-2026-papers
> 
> It could be that the data flow compiler, things sketched
> by OpenXLA already work well enough.
> 
> Mild Shock schrieb:
>> Hi,
>>
>> I am not saying anything. Thats the definition of PRAM.
>> Whats wrong with you, are you a 5 year old moron.
>> I am only citing a theoretical computer science model:
>>
>> - Concurrent read concurrent write (CRCW)—multiple
>> processors can read and write. A CRCW PRAM is sometimes
>> called a concurrent random-access machine.
>> https://en.wikipedia.org/wiki/Parallel_RAM
>>
>> Technically with multi-channel memory nowadays, it
>> doesn't need locks on the hardware level, only tiny
>> serialization, could even happen outside of the CPU.
>>
>> So if you drop some barrier requirements, you could
>> really have the chaos of a PRAM, for worse or
>> for better. I think you need to accept that,
>>
>> even if its to big to fit in your tiny squirrel brain.
>>
>> Bye
>>
>> P.S.: "effectively CREW, since only one write per address at
>> a time", it will just block the other cores? Short answer:
>> Yes — if two cores try to write the same address, one
>>
>> of them is forced to stall (block) until the other completes.
>> In real hardware, the effect can mimic CRCW behavior over
>> a short time window, even though it’s not truly simultaneous.
>>
>> this blocking usually happens in the cache-coherence
>> system, not at DRAM. Modern CPUs use MESI/MOESI. It happens
>> over a small interval [t₁, t₂] dictated by cache coherence.
>>
>>  From the POINT OF VIEW OF AN ALGORITHM, it’s “CRCW enough.”
>>
>>
>> Bosephis Otlesnov schrieb:
>>> Mild Shock wrote:
>>>
>>>> What are you, a 5 year old moron?
>>>>
>>>> There are millions of algorithm that use volatile variables. Just look
>>>> at the Java code base.
>>>>
>>>> But I was not refering to multi-threading, I was refering to PRAM for
>>>> matrix operations.
>>>
>>> i thought you said you wanna read and write parallel to RAM, aka 
>>> PRAM, let
>>> me see.. zum zum zum, yeah, you said that. Take a lock at timing
>>> requirements for a read/write cycle, deadlines etc, shared memory or 
>>> not,
>>> fucking idiot.
>>>
>>
> 

[toc] | [prev] | [next] | [standalone]

#641545 — Re: Introduction to AMBA® 4 ACE™ (2011) (Was: POINT OF VIEW OF AN ALGORITHM)

Mild Shock wrote:

> What are you squirrel brain, some russion developer controlling a drone
> from within EMACS ? Meanwhile ARM and Intel and Snapdragon etc.. have
> developed
> 
> much more marvels than only this simple PRAM.
> The excitement on the side of ARM is quite big, that they got into the
> boat of OpenAI:

if you guys from now on, are starting to write parallel to RAM, certainly
you gonna win the war; this never occurred to me. My butt, this must be
your secret weapon in the blitzkrieg

[toc] | [prev] | [next] | [standalone]

#641546 — Re: Introduction to AMBA® 4 ACE™ (2011) (Was: POINT OF VIEW OF AN ALGORITHM)

You always sound like a 5 year old imbecil.
Did they install computers in your kindergarden.
And now you are making random posts idiot russ bot.

Josbanne Balagula schrieb:
> Mild Shock wrote:
> 
>> What are you squirrel brain, some russion developer controlling a drone
>> from within EMACS ? Meanwhile ARM and Intel and Snapdragon etc.. have
>> developed
>>
>> much more marvels than only this simple PRAM.
>> The excitement on the side of ARM is quite big, that they got into the
>> boat of OpenAI:
> 
> if you guys from now on, are starting to write parallel to RAM, certainly
> you gonna win the war; this never occurred to me. My butt, this must be
> your secret weapon in the blitzkrieg
> 

[toc] | [prev] | [standalone]

Back to top | Article view | sci.math

csiph-web