From stdcxx-dev-return-1380-apmail-incubator-stdcxx-dev-archive=incubator.apache.org@incubator.apache.org Tue May 23 13:45:50 2006
Return-Path:
Delivered-To: apmail-incubator-stdcxx-dev-archive@www.apache.org
Received: (qmail 91161 invoked from network); 23 May 2006 13:45:50 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
by minotaur.apache.org with SMTP; 23 May 2006 13:45:50 -0000
Received: (qmail 68211 invoked by uid 500); 23 May 2006 13:45:50 -0000
Delivered-To: apmail-incubator-stdcxx-dev-archive@incubator.apache.org
Received: (qmail 68187 invoked by uid 500); 23 May 2006 13:45:49 -0000
Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: stdcxx-dev@incubator.apache.org
Delivered-To: mailing list stdcxx-dev@incubator.apache.org
Received: (qmail 68175 invoked by uid 99); 23 May 2006 13:45:49 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2006 06:45:49 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of AntonP@moscow.vdiweb.com designates 195.210.189.132 as permitted sender)
Received: from [195.210.189.132] (HELO mail.moscow.vdiweb.com) (195.210.189.132)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2006 06:45:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Intel 9.1.0.22 compiler
Date: Tue, 23 May 2006 17:45:23 +0400
Message-ID: <4D6A8407B7AC6F4D95B0E55C4E7C4C6204404678@exmsk.moscow.vdiweb.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Intel 9.1.0.22 compiler
Thread-Index: AcZ94jqu02nAWUxLSPGVp7/n7ZbJfwAgW5jA
From: "Anton Pevtsov"
To:
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N
Martin Sebor wrote:
> The exception specification warning is most likely caused by
> a configuration bug and something to look into. Could you open an
issue please?
The jira issue created:
http://issues.apache.org/jira/browse/STDCXX-187
Martin Sebor wrote:
> Ditto for the one about _C_name.
The jira issue created:
http://issues.apache.org/jira/browse/STDCXX-188
Martin Sebor wrote:
> We will want to continue to support both for some time but I wouldn't
spend too much time updating the script to accommodate the Unicode logs
(unless you would like to use the compiler and > find the logs useful).
We will be changing the log format to look the same across all platforms
at some point in the near future anyway.
I updated the script to incorporate icc-9.1 into supported
configurations. It required minor changes to several script files. The
changes are here:
http://people.apache.org/~antonp/stdcxx05232006/Scripts/
Change log:
2006-05-23 Anton Pevtsov
* data.js (icc91SolutionName, icc91CfgSolutionName): New global
variables to keep icc-9.1 solution names.
* generate.js (solutionICC91): New global variable to keep
icc-9.1=20
solution object.
* generate.wsf (generateBuildBatch): Added special processing=20
for icc-9.1solution.
* icc-config.js (solutionICC91Cfg): New variable to keep icc-9.1
configuration solution.
(configureToolsICC91): New function to configure tools for
icc-9.1.
* makelog.wsf (readAndCheckArguments): Set buildLogUnicode=20
variable to -1 for icc-9.1 - buildlog.htm is unicode.
* msvc-config.js (solutionICC91): New variable to keep icc-9.1=20
solution object.
* runall.wsf (runAllExamples): Set logUnicode variable to "true"
for icc-9.1 - buildlog.htm is unicode.
May I commit these changes?
Thanks,
Anton Pevtsov
-----Original Message-----
From: Martin Sebor [mailto:sebor@roguewave.com]=20
Sent: Tuesday, May 23, 2006 00:57
To: stdcxx-dev@incubator.apache.org
Subject: Re: Intel 9.1.0.22 compiler
Anton Pevtsov wrote:
> Martin, I tested our solution generation script against new Intel=20
> compiler 9.1.0.22. The library builds successful, but produces several
> warnings. see the attached file, please.
The dllexport/import warnings look suspicious to me. The members in
question are defined in a dll-exported specialization so there should be
no need to repeat it in their definition as well. MSVC doesn't issue
them so I suspect it's an Intel bug but would need a small test case to
say so definitively.
The exception specification warning is most likely caused by
a configuration bug and something to look into. Could you open an issue
please? Ditto for the one about _C_name.
I believe warning #279 (controlling expression constant) has been
removed from recent versions of the EDG front end (or at least can be
silenced by negating the constant) so it seems that Intel hasn't updated
their version yet. I'm not sure how to silence it without turning the
constant into a runtime variable.
> Tests and examples builds and works ok.
>=20
> But the BuildLog.htm files become unicode, so it is necessary to=20
> update the script. I can do it, but there is a question: is it=20
> necessary to keep both 9.0 and 9.1 compilers?
We will want to continue to support both for some time but I wouldn't
spend too much time updating the script to accommodate the Unicode logs
(unless you would like to use the compiler and find the logs useful). We
will be changing the log format to look the same across all platforms at
some point in the near future anyway.
Martin