On 03/12/2007, Graeme Geldenhuys <[EMAIL PROTECTED]> wrote:
> > .
> > Well, OS/2 supports SMP on up to 64 CPUs... If I remember correctly, the
> > first version supporting SMP was OS/2 v2.11 dating back to July 1994.
> >
A quick Google search confirms our thoughts. SMP was indeed in OS/2 2.11.
h
On 03/12/2007, Tomas Hajny <[EMAIL PROTECTED]> wrote:
> >
> > IBM implemented threads but as I understand it had no support for
> > parallelisation across multiple processors, either SMP/NUMA or cluster.
> .
> Well, OS/2 supports SMP on up to 64 CPUs... If I remember correctly, the
> first version
Mark Morgan Lloyd wrote:
> Graeme Geldenhuys wrote:
>
>> Anybody that's ever programmed multi-threaded applications knows it's
>> a daunting task and there is a lot as scope for errors. With all
>> these new multi-core processors coming into the market, application
>> developer need to starting sh
Graeme Geldenhuys wrote:
Anybody that's ever programmed multi-threaded applications knows it's
a daunting task and there is a lot as scope for errors. With all
these new multi-core processors coming into the market, application
developer need to starting shifting their mindset from serial
progr
On 03 Dec 2007, at 08:44, Florian Klaempfl wrote:
Making such tests is not easy because they depend on the system
locale.
Using only latin characters make it work on all systems but with latin
only also the default implemenation works and renders the test
useless.
Using non-latin character
Here is a start:
http://wiki.lazarus.freepascal.org/OpenMP_support
Thanks for the link.
I'll add my "thread event" idea as another proposal.
-Michael
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/li
I found this on the web Anybody think it viable to patch FPC? :-)
function GetRandomNumber: Integer;
begin
Result := 4; // Chosen by fair dice roll. Guaranteed to be random.
end;
Original source:
http://xkcd.com/221/
Regards,
- Graeme -
Hi...
I have to bother you to solve that problem... Compiling I get that errors:
/usr/lib/fpc/2.2.1/units/x86_64-linux/rtl/cthreads.o: In function
`CTHREADS_LOADPTHREADS$$BOOLEAN':cthreads.pp:(.text+0x11): warning:
Using 'dlopen' in statically linked applications requires at runtime the
shared
On Mon, 3 Dec 2007 10:16:17 +0100
"Helmut Hartl" <[EMAIL PROTECTED]> wrote:
>[...]
> Also "Open-MPI" sounds very interesting. But i fear a "no brain
> solution API" for developers does not exist -
> and without digging deeper into the problems of that field someone
> would have many hours of time
Very true words (all of them, technical an political ones).
Multithreading (an thus multiprocessing which requires same) does not
help a bit if the problems of protecting data accesses is not decently
solved.
-Michael
___
fpc-devel maillist - fpc-
On Mon, 03 Dec 2007 11:47:10 +0100
Michael Schnell <[EMAIL PROTECTED]> wrote:
> There are implementations of "parallel" and "sequential" sections in
> some programming languages. Of course FPGA description languages like
> VHDL or Verilog do this from ground up, but there are also C derivate
> s
I kind-of understand that... Borland tried to encapsulate the whole
threading thing in a TThread class. It made it easier and every bit
helps!
Agreed.
But while the current implementation is absolutely appropriate for many
tasks, it _could_ be a lot more usable if in many other cases when
There are implementations of "parallel" and "sequential" sections in
some programming languages. Of course FPGA description languages like
VHDL or Verilog do this from ground up, but there are also C derivate s
that allow for parallelism in appropriately defined sections of code. I
suppose it's
I suppose we are discussing the Delphi language keyword "interface" and
it's implementation in free pascal.
-Michael
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
>> One advantage is that it can be easely used on many languages,
>> althougth the usefulness of that for ideintf is probably very small.
>>
>I suppose you mean programming languages not spoken languages.
>But Interface is a Delphi language keyword. I don't see what this has
to with C or whate
>I kind-of understand that... Borland tried to encapsulate the whole
threading thing in a TThread class. It made it easier and every bit
helps! I simply thought I should >mention it here, so that FPC
developers know about this new API. I haven't had a look at their API
docs yet, but thought if
One advantage is that it can be easely used on many languages,
althougth the usefulness of that for ideintf is probably very small.
I suppose you mean programming languages not spoken languages.
But Interface is a Delphi language keyword. I don't see what this has to
with C or whatever.
On Monday 03 December 2007 09:20, Graeme Geldenhuys wrote:
> On 03/12/2007, Marco van de Voort <[EMAIL PROTECTED]> wrote:
> > That is an open door that has been kicked in by all vendors. The
> > problem is
>
> I kind-of understand that... Borland tried to encapsulate the whole
> threading thing in
On 03/12/2007, Marco van de Voort <[EMAIL PROTECTED]> wrote:
>
> That is an open door that has been kicked in by all vendors. The problem is
I kind-of understand that... Borland tried to encapsulate the whole
threading thing in a TThread class. It made it easier and every bit
helps! I simply th
19 matches
Mail list logo
