On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
## The Next Meetings
We had our October monthly meeting one week after this meeting.
The next quarterly should happen on January 5, 2024. We had no
regular planning sessions in October, but two workgroup
meetings took place
On Monday, 11 December 2023 at 19:55:38 UTC, Timon Gehr wrote:
There is the following trick. Not ideal since the length cannot
be inferred, but this successfully injects alloca into the
caller's scope.
Wow, what a great hack - I'd have never came up with that!
On Monday, 11 December 2023 at 19:55:38 UTC, Timon Gehr wrote:
... this successfully injects alloca into the caller's scope.
```d
import core.stdc.stdlib:alloca;
import std.range:ElementType;
import core.lifetime:moveEmplace;
struct VLA(T,alias len){
T[] storage;
this(R)(R
On Monday, 11 December 2023 at 08:24:55 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson
wrote:
Or you could use grep with `--output-ll` as noted by Johan
https://github.com/ldc-developers/ldc/issues/4265#issuecomment-1376424944 although this will be with
On Monday, 11 December 2023 at 22:04:34 UTC, Nicholas Wilson
wrote:
And please do get in touch with Bruce Carneal if you want some
tips and insight with the practical and applied side of
dcompute (also with auto-vectorisation) as he has used it a lot
more than I have.
dcompute needs some
On Monday, 11 December 2023 at 08:24:55 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson
wrote:
Always happy to help if you're interested in looking into
using dcompute.
Thank you, I'll let you know!
And please do get in touch with Bruce Carneal if you
On 12/11/23 20:55, Timon Gehr wrote:
There is the following trick. Not ideal since the length cannot be
inferred, but this successfully injects alloca into the caller's scope.
I see Nick already brought it up.
On 12/6/23 17:28, Mike Parker wrote:
One way to do that in D is to use `alloca`, but that's an issue because
the memory it allocates has to be used in the same function that calls
the `alloca`. So you can't, e.g., use `alloca` to alloc memory in a
constructor, and that prevents using it in
On Sunday, 10 December 2023 at 15:08:05 UTC, Bastiaan Veelo wrote:
We are looking forward to being able to safely use LDC, because
tests show that it has the potential to at least double the
performance.
Yes, and that's before you its excellent SIMD capabilities :)
On Sunday, 10 December 2023 at 22:59:06 UTC, Nicholas Wilson
wrote:
Always happy to help if you're interested in looking into using
dcompute.
Thank you, I'll let you know!
Or you could use grep with `--output-ll` as noted by Johan
On Sunday, 10 December 2023 at 18:16:05 UTC, Nick Treleaven wrote:
You can call `alloca` as a default argument to a function. The
memory will be allocated on the caller's stack before calling
the function:
https://github.com/ntrel/stuff/blob/master/util.d#L113C1-L131C2
I've just tested and it
On Sunday, 10 December 2023 at 16:08:45 UTC, Bastiaan Veelo wrote:
On Sunday, 10 December 2023 at 15:31:55 UTC, Richard (Rikki)
Andrew Cattermole wrote:
It will be interesting to hear how dcompute will fare in your
situation, due to it being D code it should be an incremental
improvement
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
One way to do that in D is to use `alloca`, but that's an issue
because the memory it allocates has to be used in the same
function that calls the `alloca`. So you can't, e.g., use
`alloca` to alloc memory in a constructor, and
On Sunday, 10 December 2023 at 17:11:04 UTC, Siarhei Siamashka
wrote:
On Sunday, 10 December 2023 at 15:08:05 UTC, Bastiaan Veelo
wrote:
The compiler can check if `scope` delegates escape a function,
but it only does this in `@safe` code --- and our code is long
from being `@safe`. So it was a
On Sunday, 10 December 2023 at 15:08:05 UTC, Bastiaan Veelo wrote:
1) Missing `scope` storage class specifiers on `delegate`
function arguments. This can be chalked down as a beginner
error, but also one that is easy to miss. If you didn't know:
without `scope` the compiler cannot be sure that
On Sunday, 10 December 2023 at 15:31:55 UTC, Richard (Rikki)
Andrew Cattermole wrote:
It will be interesting to hear how dcompute will fare in your
situation, due to it being D code it should be an incremental
improvement once you're ready to move to D fully.
Yes, dcompute could mean
That is awesome to hear!
If the move towards ldc has the potential to half your run time, that is
quite a significant improvement for your customers.
It will be interesting to hear how dcompute will fare in your situation,
due to it being D code it should be an incremental improvement once
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
Bastiaan reported that SARC had been testing their D codebase
(transpiled from Pascal---[see Bastiaan's DConf 2019
talk](https://youtu.be/HvunD0ZJqiA)). They'd found the
multithreaded performance worse than the Pascal version.
On Wednesday, 6 December 2023 at 16:28:08 UTC, Mike Parker wrote:
### Bastiaan
They'd found the multithreaded performance worse than the
Pascal version. He said that execution time increased with more
threads and that it didn't matter how many threads you throw at
it. It's the latter problem
This needs to be taken out of DRuntime because DRuntime is
distributed pre-compiled, and that ties it to a specific
compiler API, which isn't good. Instead, we should distribute
it as a package. It's something he'd brought up before.
Why not directly distribute DRuntime as a source? or
The D Language Foundation's quarterly meeting for October 2023
took place on Friday the 6th at 15:00 UTC. This was quite a short
one as far as quarterlies go, clocking in at around 35 minutes.
## The Attendees
The following people attended the meeting:
* Mathis Beer (Funkwerk)
* Walter
21 matches
Mail list logo
