On 2017-06-25 17:47, Adrian Matoga wrote:
There are other 32-bit platforms that are going to stay on the market
for a while. 32-bit ARMs won't disappear anytime soon.
Sure, but as I mentioned I mixed up ketmar and Guillaume Piolat and
Guillaume Piolat is using Apple platforms, as far as I
On Tuesday, 20 June 2017 at 11:49:49 UTC, Jacob Carlborg wrote:
You need to move to 64bit. Apple is already deprecating support
for 32bit apps and after the next version of macOS (High
Sierra) they're going to remove the support for 32bit apps.
There are other 32-bit platforms that are going
On Saturday, 24 June 2017 at 18:12:43 UTC, Dmitry Olshansky wrote:
I still think that separate pool types is better, see eg
jemalloc.
Right now this leads to some inflation of RSS cause previously
used and now freed pages can only be reused when the whole pool
(e.g. 4MB or 16MB) is free
On Saturday, 24 June 2017 at 15:31:21 UTC, Martin Nowak wrote:
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
FYI, we've tried to improve the binary pool search, but
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
"But the main unanswered question is why? Why an extra pass?"
It's likely to pave over the many pitfalls of D finalizers.
E.g. finalizers corrupting data:
class
On Tuesday, 20 June 2017 at 15:16:01 UTC, Ecstatic Coder wrote:
This is probably why Nim's author was once paid to wrap an open
source game engine (Urho3D), and improve the language's native
compatibility with C++ libraries.
https://forum.nim-lang.org/t/870
On 2017-06-20 16:16, Petar Kirov [ZombineDev] wrote:
I highly recommend watching this talk:
https://www.youtube.com/watch?v=36Ykla27FIo and browsing through this
repo: https://github.com/ionescu007/lxss which reveals many interesting
details about that part of Windows.
Looks interesting.
On Tue, Jun 20, 2017 at 07:14:11PM +, Dmitry Olshansky via Digitalmars-d
wrote:
> On Tuesday, 20 June 2017 at 16:49:44 UTC, H. S. Teoh wrote:
[...]
> Interestingly the moment you "reallocate" to expand the AA it will be
> considered a new object.
[...]
This is not entirely true. The *table*
On Tuesday, 20 June 2017 at 16:49:44 UTC, H. S. Teoh wrote:
On Tue, Jun 20, 2017 at 07:47:13AM +, Dmitry Olshansky via
Digitalmars-d wrote:
On Monday, 19 June 2017 at 23:52:16 UTC, Vladimir Panteleev
wrote:
[...]
FWIW, here's a data point to the contrary:
One of my projects involves
On 2017-06-20 16:03, Petar Kirov [ZombineDev] wrote:
I highly doubt that ketmar would have any intention of touching macOS
regardless ;)
I somehow mixed up ketmar and Guillaume Piolat (which used to go by the
alias p0nce). My mistake.
--
/Jacob Carlborg
On Tue, Jun 20, 2017 at 07:47:13AM +, Dmitry Olshansky via Digitalmars-d
wrote:
> On Monday, 19 June 2017 at 23:52:16 UTC, Vladimir Panteleev wrote:
[...]
> > - Support generational collection using write barriers implemented
> > through memory protection.
>
> Super slow sadly. That being
On Tuesday, 20 June 2017 at 15:16:01 UTC, Ecstatic Coder wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
Many thanks for your efforts Dmitry :)
May I ask you if you
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
Many thanks for your efforts Dmitry :)
May I ask you if you plan to make a soft real-time GC similar to
the one implemented
On Tuesday, 20 June 2017 at 07:11:10 UTC, Dmitry Olshansky wrote:
On Monday, 19 June 2017 at 22:50:05 UTC, Adam D. Ruppe wrote:
What is it about Windows that makes you call it a distant
possibility? Is it just that you are unfamiliar with it or is
there some specific OS level feature you plan
On Tuesday, 20 June 2017 at 11:44:41 UTC, rikki cattermole wrote:
On 20/06/2017 12:41 PM, Jacob Carlborg wrote:
On 2017-06-20 06:37, ketmar wrote:
it is higly depends of undocumented windows internals, and
not portable between windows versions. more-or-less working
implementations of
On Tuesday, 20 June 2017 at 11:49:49 UTC, Jacob Carlborg wrote:
On 2017-06-20 06:54, ketmar wrote:
[...]
You need to move to 64bit. Apple is already deprecating support
for 32bit apps and after the next version of macOS (High
Sierra) they're going to remove the support for 32bit apps.
I
On Tuesday, 20 June 2017 at 04:35:27 UTC, ketmar wrote:
H. S. Teoh wrote:
He mentioned the "fork trick", which I assume refers to how
Linux's
implementation of fork() uses copy-on-write rather than
immediately
duplicating the parent process' memory structures. There was
a D1 GC
some time
On 2017-06-20 06:54, ketmar wrote:
"...the dubious optimization of no interior pointers..."
this is the ONLY (i emphasise it!) way i were able to make my e-mail and
irc clients to not leak memory, and keep using GC. on 32-bit systems
false pointers *is* a problem, and NO_INTERIOR really
On 20/06/2017 12:41 PM, Jacob Carlborg wrote:
On 2017-06-20 06:37, ketmar wrote:
it is higly depends of undocumented windows internals, and not
portable between windows versions. more-or-less working
implementations of `fork()` were existed at least since NT3 era, but
nobody considered 'em
On 2017-06-20 01:52, Vladimir Panteleev wrote:
- More, much more debugging facilities! Integrate Diamond and Valgrind
interoperability.
Don't for get the Clang sanitizers, assuming they work using LDC.
--
/Jacob Carlborg
On 2017-06-20 06:37, ketmar wrote:
it is higly depends of undocumented windows internals, and not portable
between windows versions. more-or-less working implementations of
`fork()` were existed at least since NT3 era, but nobody considered 'em
as more than a PoC, and even next service pack
On 6/20/2017 12:04 AM, Nicholas Wilson wrote:
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
This was posted on reddit:
https://www.reddit.com/r/programming/comments/6ic52d/inside_ds_gc/
Also on hacker news.
On Monday, 19 June 2017 at 23:39:54 UTC, H. S. Teoh wrote:
On Mon, Jun 19, 2017 at 10:35:42PM +, Dmitry Olshansky via
Digitalmars-d wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
On Monday, 19 June 2017 at 23:10:43 UTC, Ali Çehreli wrote:
On 06/19/2017 03:35 PM, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one
soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
Very
On Monday, 19 June 2017 at 23:52:16 UTC, Vladimir Panteleev wrote:
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
Looks like I'm not the only one itching to have a go at D's GC
:) This will very
On Monday, 19 June 2017 at 22:50:05 UTC, Adam D. Ruppe wrote:
What is it about Windows that makes you call it a distant
possibility? Is it just that you are unfamiliar with it or is
there some specific OS level feature you plan on needing?
This is mostly because I wanted to abuse lazy commit
On Tuesday, 20 June 2017 at 02:23:48 UTC, safety0ff wrote:
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
This was posted on reddit:
Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a new one
soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
"...the dubious optimization of no interior pointers..."
this is the ONLY (i emphasise it!) way i were able to make my
safety0ff wrote:
On Monday, 19 June 2017 at 23:39:54 UTC, H. S. Teoh wrote:
On Mon, Jun 19, 2017 at 10:50:05PM +, Adam D. Ruppe via
Digitalmars-d wrote:
What is it about Windows that makes you call it a distant possibility?
Is it just that you are unfamiliar with it or is there some
H. S. Teoh wrote:
He mentioned the "fork trick", which I assume refers to how Linux's
implementation of fork() uses copy-on-write rather than immediately
duplicating the parent process' memory structures. There was a D1 GC
some time ago that depended on this behaviour to speed up the
On Monday, 19 June 2017 at 23:39:54 UTC, H. S. Teoh wrote:
On Mon, Jun 19, 2017 at 10:50:05PM +, Adam D. Ruppe via
Digitalmars-d wrote:
What is it about Windows that makes you call it a distant
possibility? Is it just that you are unfamiliar with it or is
there some specific OS level
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
Good overview, however:
the binary search pool lookup is
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
if not a single pool is capable to service an allocation a
On Monday, 19 June 2017 at 22:35:42 UTC, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
Looks like I'm not the only one itching to have a go at D's GC :)
This will very likely be my DConf 2018 project. However, I have
slightly
On Mon, Jun 19, 2017 at 10:35:42PM +, Dmitry Olshansky via Digitalmars-d
wrote:
> My take on D's GC problem, also spoiler - I'm going to build a new one
> soonish.
>
> http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
[...]
Very interesting indeed!
One question about killing
On 06/19/2017 03:35 PM, Dmitry Olshansky wrote:
My take on D's GC problem, also spoiler - I'm going to build a new one
soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
Very informative, thanks.
However, I can think of many reasons like
What is it about Windows that makes you call it a distant
possibility? Is it just that you are unfamiliar with it or is
there some specific OS level feature you plan on needing?
My take on D's GC problem, also spoiler - I'm going to build a
new one soonish.
http://olshansky.me/gc/runtime/dlang/2017/06/14/inside-d-gc.html
---
Dmitry Olshansky
40 matches
Mail list logo
