Closed arporter closed 7 years ago
Created schedule_intrinsics branch for this issue.
Currently the 'type' of an operator node is the string representing the operation itself, e.g. "+" for a node representing an addition. However, the 'type' of a node representing any intrinsic operation is just "intrinsic". Now that we need to include the cost of intrinsic operations this distinction feels awkward.
Branch merged to master. Pull request closed.
While working on #8 I've realised that the schedule generator quietly ignores the cost of any intrinsic operations - it considers only operators. This is a significant omission because the intrinsics that we do currently recognise (sin, cos, **) are computationally costly. In this issue we'll think about how we might remedy the situation.