Description

A user requested if it was possible to include the following workaround for a bug in intel 2016.1.150. Since this change looks harmless, I think we can include it.