FastMath dist

?

Percentage Accurate: 98.0% → 100.0%
Time: 1.1s
Precision: binary64
Cost: 320

?

\[d1 \cdot d2 + d1 \cdot d3 \]
↓
\[d1 \cdot \left(d2 + d3\right) \]
(FPCore (d1 d2 d3) :precision binary64 (+ (* d1 d2) (* d1 d3)))
↓
(FPCore (d1 d2 d3) :precision binary64 (* d1 (+ d2 d3)))
double code(double d1, double d2, double d3) {
	return (d1 * d2) + (d1 * d3);
}
↓
double code(double d1, double d2, double d3) {
	return d1 * (d2 + d3);
}

real(8) function code(d1, d2, d3)
    real(8), intent (in) :: d1
    real(8), intent (in) :: d2
    real(8), intent (in) :: d3
    code = (d1 * d2) + (d1 * d3)
end function
↓
real(8) function code(d1, d2, d3)
    real(8), intent (in) :: d1
    real(8), intent (in) :: d2
    real(8), intent (in) :: d3
    code = d1 * (d2 + d3)
end function

public static double code(double d1, double d2, double d3) {
	return (d1 * d2) + (d1 * d3);
}
↓
public static double code(double d1, double d2, double d3) {
	return d1 * (d2 + d3);
}

def code(d1, d2, d3):
	return (d1 * d2) + (d1 * d3)
↓
def code(d1, d2, d3):
	return d1 * (d2 + d3)

function code(d1, d2, d3)
	return Float64(Float64(d1 * d2) + Float64(d1 * d3))
end
↓
function code(d1, d2, d3)
	return Float64(d1 * Float64(d2 + d3))
end

function tmp = code(d1, d2, d3)
	tmp = (d1 * d2) + (d1 * d3);
end
↓
function tmp = code(d1, d2, d3)
	tmp = d1 * (d2 + d3);
end

code[d1_, d2_, d3_] := N[(N[(d1 * d2), $MachinePrecision] + N[(d1 * d3), $MachinePrecision]), $MachinePrecision]
↓
code[d1_, d2_, d3_] := N[(d1 * N[(d2 + d3), $MachinePrecision]), $MachinePrecision]

d1 \cdot d2 + d1 \cdot d3
↓
d1 \cdot \left(d2 + d3\right)

Local Percentage Accuracy vs ?

The average percentage accuracy by input value. Horizontal axis shows value of an input variable; the variable is choosen in the title. Vertical axis is accuracy; higher is better. Red represent the original program, while blue represents Herbie's suggestion. These can be toggled with buttons below the plot. The line is an average while dots represent individual samples.

Herbie found 1 alternatives:

AlternativeAccuracySpeedup

Accuracy vs Speed

The accuracy (vertical axis) and speed (horizontal axis) of each alternatives. Up and to the right is better. The red square shows the initial program, and each blue circle shows an alternative.The line shows the best available speed-accuracy tradeoffs.

Bogosity?

Bogosity

Try it out?

Your Program's Arguments

Results

Enter valid numbers for all inputs

Target

Original98.0%
Target100.0%
Herbie100.0%
\[d1 \cdot \left(d2 + d3\right) \]

Derivation?

  1. Initial program 97.6%

    \[d1 \cdot d2 + d1 \cdot d3 \]

  2. Simplified100.0%

    \[\leadsto \color{blue}{d1 \cdot \left(d2 + d3\right)} \]
    Step-by-step derivation

    [Start]97.6%

    \[ d1 \cdot d2 + d1 \cdot d3 \]

    distribute-lft-out [=>]100.0%

    \[ \color{blue}{d1 \cdot \left(d2 + d3\right)} \]

  3. Final simplification100.0%

    \[\leadsto d1 \cdot \left(d2 + d3\right) \]

Reproduce?

herbie shell --seed 2023178 
(FPCore (d1 d2 d3)
  :name "FastMath dist"
  :precision binary64

  :herbie-target
  (* d1 (+ d2 d3))

  (+ (* d1 d2) (* d1 d3)))