$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] checking __INTEL_COMPILER == 9999
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2015-11-14 06:56:49
On 2015-11-13 22:45, Blower, Melanie wrote:
> A few years ago, circa 2010, the Intel 12.x compiler was released
> without having a correct value for the macro __INTEL_COMPILER. It
> was released using the development-only version number 9999 instead
> of the correct value 12xx. Later on, an Intel 12.x compiler was
> updated to remove this problem and the version number made correct.
>
> Meanwhile, since boost needed to add some workarounds, there was code
> added in a couple of boost files to check for version 9999. The
> check for 9999 in boost causes trouble in our current development
> compiler in-house testing. Is it possible to have this version
> checking removed from the boost sources? There's no advantage to
> boost users, and possibly a disadvantage if someone is still using a
> not-updated 12.x compiler. But hopefully that is unlikely, we're
> currently shipping our 16.x compiler.
Since this basically means removing support for the broken 12.x release,
that may be a difficult decision.
Is it possible to distinguish your current development builds from the
broken 12.x release? If there was a macro to do that it might be better
to add that macro to the preprocessor conditions.