https://github.com/CyberShadow/DustMite/wiki
On Thursday, 21 May 2015 at 08:28:30 UTC, Saurabh Das wrote:
Hello,
We have been working on a genetic programming project, and
occasionally the compiler fails and gives an internal error.
I've captured and reduced one of these down to a single
Hello,
We have been working on a genetic programming project, and
occasionally the compiler fails and gives an internal error. I've
captured and reduced one of these down to a single expression.
See http://dpaste.dzfl.pl/e7a66aa067ab (reduced_expr.d)
When I compile this file using: dmd -c
Thanks!
Wow, dustmite is really useful. It reduces the expression down to:
double someFunction(double AvgPriceChangeNormalized, double
TicksTenMinutesNormalized)
{
return
(TicksTenMinutesNormalized?1:AvgPriceChangeNormalized)?1:TicksTenMinutesNormalized/(TicksTenMinutesNormalized==0)==0;
On Thursday, May 21, 2015 08:28:29 Saurabh Das via Digitalmars-d-learn wrote:
Am I correct in assuming that an internal error in the compiler
should be filed as a bug report?
Yes. You should never see an ICE, and the compiler should never segfault.
So, whenever you see either of those happen,
double foo(double b)
{
return b / (b == 0) == 0;
}
Looks like this fails too.
PS: The original expression:
http://dpaste.dzfl.pl/raw/e7a66aa067ab
double someFunction(double AvgPriceChangeNormalized, double
DayFactor, double TicksTenMinutesNormalized)
{
return
and please submit to https://issues.dlang.org
Submitted: https://issues.dlang.org/show_bug.cgi?id=14613
That expression is, not to put too fine a point on it, mad.
The operator precedence itself is giving me a headache, let
alone the division of a double by a boolean... I'm pretty sure
On Thursday, 21 May 2015 at 08:55:45 UTC, Saurabh Das wrote:
Thanks!
Wow, dustmite is really useful. It reduces the expression down
to:
double someFunction(double AvgPriceChangeNormalized, double
TicksTenMinutesNormalized)
{
return
On Thursday, 21 May 2015 at 10:24:59 UTC, John Colvin wrote:
On Thursday, 21 May 2015 at 08:55:45 UTC, Saurabh Das wrote:
Thanks!
Wow, dustmite is really useful. It reduces the expression down
to:
double someFunction(double AvgPriceChangeNormalized, double
TicksTenMinutesNormalized)
{
On Thu, 21 May 2015 11:36:14 +, Saurabh Das wrote:
PS: The original expression:
http://dpaste.dzfl.pl/raw/e7a66aa067ab
double someFunction(double AvgPriceChangeNormalized, double DayFactor,
double TicksTenMinutesNormalized)
{
return
fair enough. I thought normally you'd want to have some sort of
expression simplification in genetic programming, to avoid
adding too many superfluous degrees of freedom? Aside from the
obvious problems, those extra degrees of freedom can put you at
risk of overfitting.
Yes - our
On Thursday, 21 May 2015 at 11:36:15 UTC, Saurabh Das wrote:
PS: The original expression:
http://dpaste.dzfl.pl/raw/e7a66aa067ab
double someFunction(double AvgPriceChangeNormalized, double
DayFactor, double TicksTenMinutesNormalized)
{
return
If you're looking for speed, how about ldc?
On Thursday, 21 May 2015 at 14:12:25 UTC, Kagamin wrote:
If you're looking for speed, how about ldc?
Absolutely - we are working on getting it to compile on ldc
and/or gdc.
14 matches
Mail list logo
