https://www.reddit.com/r/programming/comments/5v43p6/d_language_gets_more_points_than_c_in_digitalwhip/
Ali
On Saturday, 13 February 2016 at 19:19:46 UTC, Johan Engelen
wrote:
On Saturday, 13 February 2016 at 18:48:12 UTC, artemalive wrote:
DigitalWhip is a performance benchmark of statically typed
programming languages that
compile to native code:
https://github.com/artemalive/DigitalWhip
Could
On Saturday, 13 February 2016 at 21:10:11 UTC, Adam D. Ruppe
wrote:
We should run benchmarks with bounds checking enabled to better
reflect real world results. Yes, it might "lose" to C
Like for like comparisons are the best approach, making it clear
what a given result is for. The most
On Sunday, 14 February 2016 at 18:07:00 UTC, artemalive wrote:
Thanks. Good suggestion. I'll check if the version information
can be retrieved automatically for all compilers. If that's the
case then version information will be added soon.
I would simply print the output of "--version" for
On Sunday, 14 February 2016 at 19:29:54 UTC, Vladimir Panteleev
wrote:
I think that in the context of a render farm, disabling bounds
checking is completely reasonable. Bugs will manifest as
crashes or rendering artifacts, and there is no risk of code
execution exploits.
But nobody would
On Sunday, 14 February 2016 at 17:31:37 UTC, artemalive wrote:
From ldc output:
"-release - Disables asserts, invariants, contracts and
boundscheck".
We (LDC team) should clarify this description. In D2, -release
does not disable bounds-checking for @safe code anymore.
-singleobj really
On Saturday, 13 February 2016 at 21:10:11 UTC, Adam D. Ruppe
wrote:
On Saturday, 13 February 2016 at 20:45:41 UTC, David Nadlinger
wrote:
Your scripts had bounds checking enabled for LDC but not the
other two D compilers.
I strongly recommend people to always keep bounds checking
enabled in
On Sunday, 14 February 2016 at 18:12:03 UTC, David Nadlinger
wrote:
On Sunday, 14 February 2016 at 17:31:37 UTC, artemalive wrote:
From ldc output:
"-release - Disables asserts, invariants, contracts and
boundscheck".
We (LDC team) should clarify this description. In D2, -release
does not
On Sunday, 14 February 2016 at 17:38:54 UTC, artemalive wrote:
Hi Adam, I'll check the influence of enabled bounds check on
benchmark result. Did not try this before.
If you do, then you should use bounds checks in C++ too. (STL
container.at(index) )
On Saturday, 13 February 2016 at 19:26:39 UTC, artemalive wrote:
On Saturday, 13 February 2016 at 19:19:46 UTC, Johan Engelen
wrote:
Could you add the compiler versions to the outputted .txt
file, e.g. `dmd --version`? (the example output files don't
have it)
These files are just for
On Sunday, 14 February 2016 at 17:43:01 UTC, Ola Fosheim Grøstad
wrote:
On Sunday, 14 February 2016 at 17:38:54 UTC, artemalive wrote:
Hi Adam, I'll check the influence of enabled bounds check on
benchmark result. Did not try this before.
If you do, then you should use bounds checks in C++
On Saturday, 13 February 2016 at 20:45:41 UTC, David Nadlinger
wrote:
Hi Artem,
On Saturday, 13 February 2016 at 18:48:12 UTC, artemalive wrote:
https://github.com/artemalive/DigitalWhip
Your scripts had bounds checking enabled for LDC but not the
other two D compilers. I posted a pull
On Saturday, 13 February 2016 at 21:10:11 UTC, Adam D. Ruppe
wrote:
On Saturday, 13 February 2016 at 20:45:41 UTC, David Nadlinger
wrote:
Your scripts had bounds checking enabled for LDC but not the
other two D compilers.
I strongly recommend people to always keep bounds checking
enabled in
compilers. If that's the
case then version information will be added soon. The thing I
don't want to do is to ask user manually to specify compiler
version in config.py, since it's easy to forget to updated it and
also I like to keep config.py as simple as possible.
At the moment DigitalWh
Dear Community,
I've prepared a valentine for you;)
It's a project I've been working for the last few months in my
free time.
DigitalWhip is a performance benchmark of statically typed
programming languages that
compile to native code: https://github.com/artemalive/DigitalWhip
D is fast
On Saturday, 13 February 2016 at 18:48:12 UTC, artemalive wrote:
DigitalWhip is a performance benchmark of statically typed
programming languages that
compile to native code:
https://github.com/artemalive/DigitalWhip
Could you add the compiler versions to the outputted .txt file,
e.g. `dmd
On Saturday, 13 February 2016 at 19:19:46 UTC, Johan Engelen
wrote:
On Saturday, 13 February 2016 at 18:48:12 UTC, artemalive wrote:
DigitalWhip is a performance benchmark of statically typed
programming languages that
compile to native code:
https://github.com/artemalive/DigitalWhip
Could
Hi Artem,
On Saturday, 13 February 2016 at 18:48:12 UTC, artemalive wrote:
https://github.com/artemalive/DigitalWhip
Your scripts had bounds checking enabled for LDC but not the
other two D compilers. I posted a pull request with the fix. LDC
isn't unreasonably slow any longer on a random
On Saturday, 13 February 2016 at 20:45:41 UTC, David Nadlinger
wrote:
Your scripts had bounds checking enabled for LDC but not the
other two D compilers.
I strongly recommend people to always keep bounds checking
enabled in real world programs because it is so useful in keeping
programs
On Saturday, 13 February 2016 at 18:48:12 UTC, artemalive wrote:
Dear Community,
I've prepared a valentine for you;)
It's a project I've been working for the last few months in my
free time.
DigitalWhip is a performance benchmark of statically typed
programming languages that
compile
20 matches
Mail list logo
