Numeric.Interval.Internal:scale from intervals-0.7.1, B

Percentage Accurate: 100.0% → 100.0%
Time: 1.6s
Alternatives: 1
Speedup: 1.5×

Specification

?
\[\begin{array}{l} \\ \frac{x \cdot y}{2} \end{array} \]
(FPCore (x y) :precision binary64 (/ (* x y) 2.0))
double code(double x, double y) {
	return (x * y) / 2.0;
}

real(8) function code(x, y)
    real(8), intent (in) :: x
    real(8), intent (in) :: y
    code = (x * y) / 2.0d0
end function

public static double code(double x, double y) {
	return (x * y) / 2.0;
}

def code(x, y):
	return (x * y) / 2.0

function code(x, y)
	return Float64(Float64(x * y) / 2.0)
end

function tmp = code(x, y)
	tmp = (x * y) / 2.0;
end

code[x_, y_] := N[(N[(x * y), $MachinePrecision] / 2.0), $MachinePrecision]

\begin{array}{l}

\\
\frac{x \cdot y}{2}
\end{array}

Sampling outcomes in binary64 precision:

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.

Accuracy vs Speed?

Herbie found 1 alternatives:

AlternativeAccuracySpeedup
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.

Initial Program: 100.0% accurate, 1.0× speedup?

\[\begin{array}{l} \\ \frac{x \cdot y}{2} \end{array} \]
(FPCore (x y) :precision binary64 (/ (* x y) 2.0))
double code(double x, double y) {
	return (x * y) / 2.0;
}

real(8) function code(x, y)
    real(8), intent (in) :: x
    real(8), intent (in) :: y
    code = (x * y) / 2.0d0
end function

public static double code(double x, double y) {
	return (x * y) / 2.0;
}

def code(x, y):
	return (x * y) / 2.0

function code(x, y)
	return Float64(Float64(x * y) / 2.0)
end

function tmp = code(x, y)
	tmp = (x * y) / 2.0;
end

code[x_, y_] := N[(N[(x * y), $MachinePrecision] / 2.0), $MachinePrecision]

\begin{array}{l}

\\
\frac{x \cdot y}{2}
\end{array}

Alternative 1: 100.0% accurate, 1.5× speedup?

\[\begin{array}{l} \\ \left(y \cdot x\right) \cdot 0.5 \end{array} \]
(FPCore (x y) :precision binary64 (* (* y x) 0.5))
double code(double x, double y) {
	return (y * x) * 0.5;
}

real(8) function code(x, y)
    real(8), intent (in) :: x
    real(8), intent (in) :: y
    code = (y * x) * 0.5d0
end function

public static double code(double x, double y) {
	return (y * x) * 0.5;
}

def code(x, y):
	return (y * x) * 0.5

function code(x, y)
	return Float64(Float64(y * x) * 0.5)
end

function tmp = code(x, y)
	tmp = (y * x) * 0.5;
end

code[x_, y_] := N[(N[(y * x), $MachinePrecision] * 0.5), $MachinePrecision]

\begin{array}{l}

\\
\left(y \cdot x\right) \cdot 0.5
\end{array}
Derivation

  1. Initial program 100.0%

    \[\frac{x \cdot y}{2} \]
  2. Add Preprocessing
  3. Step-by-step derivation

    1. lift-/.f64N/A

      \[\leadsto \color{blue}{\frac{x \cdot y}{2}} \]

    2. div-invN/A

      \[\leadsto \color{blue}{\left(x \cdot y\right) \cdot \frac{1}{2}} \]

    3. lower-*.f64N/A

      \[\leadsto \color{blue}{\left(x \cdot y\right) \cdot \frac{1}{2}} \]

    4. lift-*.f64N/A

      \[\leadsto \color{blue}{\left(x \cdot y\right)} \cdot \frac{1}{2} \]

    5. *-commutativeN/A

      \[\leadsto \color{blue}{\left(y \cdot x\right)} \cdot \frac{1}{2} \]

    6. lower-*.f64N/A

      \[\leadsto \color{blue}{\left(y \cdot x\right)} \cdot \frac{1}{2} \]

    7. metadata-eval100.0

      \[\leadsto \left(y \cdot x\right) \cdot \color{blue}{0.5} \]

  4. Applied rewrites100.0%

    \[\leadsto \color{blue}{\left(y \cdot x\right) \cdot 0.5} \]
  5. Add Preprocessing

Reproduce

?
herbie shell --seed 2024313 
(FPCore (x y)
  :name "Numeric.Interval.Internal:scale from intervals-0.7.1, B"
  :precision binary64
  (/ (* x y) 2.0))