Bug with GC fullCollect() in multithreaded environment. Grauzone explained it
here
http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=99610
Test case that freezes app (tested on 1.053):
import std.c.stdlib;
import std.stdio;
import std.gc;
import std.thread;
i
Sean Kelly Wrote:
> dsimcha Wrote:
>
> > == Quote from Sean Kelly (s...@invisibleduck.org)'s article
> > > dsimcha Wrote:
> > > >
> > > > This is great for super-scalable concurrency, the kind you need for
> > > > things like
> > > > servers, but what about the case where you need concurrency mo
Álvaro Castro-Castilla Wrote:
>
> Language extensions for message passing, such as Kilim for Java send messages
> giving away the ownership of data, not copying it. That's a reason for the
> need of compiler/runtime support.
Knowledge of unique ownership can obviate the need for copying, but co
== Quote from Sean Kelly (s...@invisibleduck.org)'s article
> �lvaro Castro-Castilla Wrote:
> >
> > Language extensions for message passing, such as Kilim for Java send
> > messages
giving away the ownership of data, not copying it. That's a reason for the need
of
compiler/runtime support.
> Know
dsimcha:
> The exception, though, is when someone is using a construct that would only be
> used by people who really need efficiency, and thus has already explicitly
> asked
> for efficiency. This includes parallel foreach. In these cases, I think that
> "efficiency first, safety second" has to
dsimcha Wrote:
> == Quote from Sean Kelly (s...@invisibleduck.org)'s article
> > Álvaro Castro-Castilla Wrote:
> > >
> > > Language extensions for message passing, such as Kilim for Java send
> > > messages
> giving away the ownership of data, not copying it. That's a reason for the
> need of
>
http://shootout.alioth.debian.org/u64q/benchmark.php?test=threadring&lang=all
2.3Go 6g 8g #3 20.6120.613,272347 0% 100% 0% 0%
Interestingly, the CPU load is kind of comical for something spawning
so many threads.
Anyone good at optimized D feel like commiting a version of this?
On Fri, Dec 11, 2009 at 12:53 PM, S < wrote:
> http://shootout.alioth.debian.org/u64q/benchmark.php?test=threadring&lang=all
>
> 2.3Go 6g 8g #3 20.6120.613,272347 0% 100% 0% 0%
>
> Interestingly, the CPU load is kind of comical for something spawning so
> many threads.
>
> Anyone good at optimize
Bill Baxter:
> D used to be there, but the folks running the shootout de-listed it
> for some reason.
> Maybe it was lack of a 64-bit compiler?
I think the notgentle person that manages the Shootout site has removed D
because D programs were too much similar to the C programs. He is looking for
On Fri, Dec 11, 2009 at 1:17 PM, bearophile wrote:
> Bill Baxter:
>> D used to be there, but the folks running the shootout de-listed it
>> for some reason.
>> Maybe it was lack of a 64-bit compiler?
>
> I think the notgentle person that manages the Shootout site has removed D
> because D program
== Quote from bearophile (bearophileh...@lycos.com)'s article
> Bill Baxter:
> > D used to be there, but the folks running the shootout de-listed it
> > for some reason.
> > Maybe it was lack of a 64-bit compiler?
> I think the notgentle person that manages the Shootout site has removed D
because D
Bill Baxter Wrote:
> Hmm. And Go qualifies because it has some CSP implementation built in?
> Or is it more because it has a billion-dollar company built in? Kinda
> makes you wonder.
>
> --bb
Yeah, and if you look at the "Alternatives" to C++ on this page, C and Go are
mentioned, but not D b
== Quote from Bill Baxter (wbax...@gmail.com)'s article
> Maybe it was lack of a 64-bit compiler?
Hint, hint, hint. I will be forever grateful to whoever makes it so I can use
>4GB of RAM in D2. (Ancient versions of D2 don't count.) Then again, these
benchmarks are focused on D1, for which a 64
bearophile wrote:
Bill Baxter:
D used to be there, but the folks running the shootout de-listed it
for some reason.
Maybe it was lack of a 64-bit compiler?
I think the notgentle person that manages the Shootout site has removed D
because D programs were too much similar to the C programs. He
On Fri, 11 Dec 2009, "J?r?me M. Berger" wrote:
> bearophile wrote:
> > Bill Baxter:
> > > D used to be there, but the folks running the shootout de-listed it
> > > for some reason.
> > > Maybe it was lack of a 64-bit compiler?
> >
> > I think the notgentle person that manages the Shootout site ha
dsimcha:
> Yeah, I think it would be much more interesting (for C++ as well as D) to see
> benchmarks in idiomatic D style. This will likely be slower than code
> written in
> the C-like subset, as there is really not much reason why C-like D code
> should be
> any slower than C. However, it w
Brad Roberts Wrote:
> This community has a lot of bad habits. The particularly dangerous one
> demonstrated well in this thread is that of making assumptions about
> intent. D isn't listed in the shootout, it once was. We don't know the
> facts about why so we like to make the up. Its human
I build dwt-win & dwtx with dmd 1.053 & tango trunk on win32 .
the execute file size is huge.
I build dwt-samples\jface.text\Simple.d, the execute file size is
24051kb, the file has 21733kb binary value is 0xff & 0x00, after upx
compress the file size is 1034kb.
I want to know is the optlink
bearophile:
> I think the notgentle person that manages the Shootout site has removed D
> because D programs were too much similar to the C programs.
I removed D because I started measuring on 4 different os/machine configurations
instead of just 1 machine.
https://alioth.debian.org/forum/forum.p
Bill Baxter:
> And Go qualifies because it has some CSP implementation built in?
Go qualifies for the moment - it's an experiment - maybe it'll turn out not to
be
so interesting after all, and in golang.org forums they'll speculate about why
it
was removed from the benchmarks game...
Brad wrote:
> This community has a lot of bad habits. The particularly dangerous one
> demonstrated well in this thread is that of making assumptions about
> intent. D isn't listed in the shootout, it once was. We don't know the
> facts about why so we like to make the up. Its human. But it's
On Fri, Dec 11, 2009 at 4:55 PM, Isaac Gouy wrote:
> Bill Baxter:
>> And Go qualifies because it has some CSP implementation built in?
>
> Go qualifies for the moment - it's an experiment - maybe it'll turn out not
> to be
> so interesting after all, and in golang.org forums they'll speculate abo
Isaac Gouy wrote:
I removed D because I started measuring on 4 different os/machine configurations
instead of just 1 machine.
https://alioth.debian.org/forum/forum.php?forum_id=2839
The link appears to be dead.
Jesse Phillips at "Fri, 11 Dec 2009 18:43:30 -0500" wrote:
JP> The comment I made, I had talked to the author of the site and the reasons
for not having D were not consistent with having Go on there.
JP> And I do believe someone did have communication with the Shootout
maintainer and the re
Walter Bright wrote:
> The link appears to be dead.
The link appears to work just fine from Mozilla Firefox.
Walter Bright:
> > https://alioth.debian.org/forum/forum.php?forum_id=2839
>
> The link appears to be dead.
It's a little complex, you have to be logged in, or you have to accept some
unsafe connections over a https.
My suggestion is to ignore the whole thing and thread, you have better things
Bane, el 11 de diciembre a las 06:00 me escribiste:
> Bug with GC fullCollect() in multithreaded environment. Grauzone explained it
> here
> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=99610
>
> Test case that freezes app (tested on 1.053):
>
>
> import
Leandro Lucarella Wrote:
> Bane, el 11 de diciembre a las 06:00 me escribiste:
> > Bug with GC fullCollect() in multithreaded environment. Grauzone explained
> > it here
> > http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=99610
To be perfectly safe, it's a t
Sean Kelly wrote:
Leandro Lucarella Wrote:
Bane, el 11 de diciembre a las 06:00 me escribiste:
Bug with GC fullCollect() in multithreaded environment. Grauzone
explained it here
http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=99610
To be perfectly safe,
Leandro Lucarella wrote:
I want to be sure the bug is present before the patch and fixed after the
patch before submiting the patch via Bugzilla.
It's a good fix, I checked in a patch for it.
I'm thinking of giving another try to writing a plotting library for D. I'm
trying to decide what GUI library to use. Here's what's important to me, in
order of importance. Someone who's more familiar with the GUI library
situation than I am please make a recommendation.
1. Good D2 support. I
"Isaac Gouy" wrote in message
news:hfurj4$1n9...@digitalmars.com...
> Walter Bright wrote:
>> The link appears to be dead.
>
> The link appears to work just fine from Mozilla Firefox.
I'm on firefox, and it's giving me some problem with the certificate.
dsimcha дµ½:
> I'm thinking of giving another try to writing a plotting library for D. I'm
> trying to decide what GUI library to use. Here's what's important to me, in
> order of importance. Someone who's more familiar with the GUI library
> situation than I am please make a recommendation.
>
dsimcha дµ½:
> I'm thinking of giving another try to writing a plotting library for D. I'm
> trying to decide what GUI library to use. Here's what's important to me, in
> order of importance. Someone who's more familiar with the GUI library
> situation than I am please make a recommendation.
>
34 matches
Mail list logo
