Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of AntonP@moscow.vdiweb.com
 designates 195.210.189.132 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: ICL 9.1 codegeneration bug (rw_char.h)
Date: Fri, 30 Jun 2006 20:22:43 +0400
Message-ID: <4D6A8407B7AC6F4D95B0E55C4E7C4C6204793D5E@exmsk.moscow.vdiweb.com>
Thread-Topic: ICL 9.1 codegeneration bug (rw_char.h)
Thread-Index: Acabr5p9vu+OrMYwQHqpzbeGVudguQAqr7/g
From: "Anton Pevtsov" <AntonP@moscow.vdiweb.com>
To: <stdcxx-dev@incubator.apache.org>

Martin Sebor wrote:
> Anton, could you please file a bug with Intel for this problem (using
your Premier Support account at http://premier.intel.com) and copy   >
the Intel bug link into the Jira issue for reference?

The jira issue was opened:
http://issues.apache.org/jira/browse/STDCXX-248

The bug was reported to Intel:
https://premier.intel.com/premier/IssueDetail.aspx?IssueID=3D380635


Thanks,
Anton Pevtsov

-----Original Message-----
From: Martin Sebor [mailto:sebor@roguewave.com]=20
Sent: Thursday, June 29, 2006 23:09
To: stdcxx-dev@incubator.apache.org
Subject: Re: ICL 9.1 codegeneration bug (rw_char.h)


Farid Zaripov wrote:
>    When I compiled 21.string.io.cpp using Intel C++ 9.1 I've found=20
> that
> a number of rw_asserts is different than with using MSVC++ 7.1.
>=20
>    I investigated this and detected the problem in UserInt::to_char()
> method.
>=20
[...]
>    I attached the test case to illustrate the problem.

Nicely done, thanks! Could you please open a Jira issue for this
compiler bug (see or of the other similar bugs for an example:
http://tinyurl.com/zrgcw). Once we have a bug number Anton or I can
commit your proposed fix (and reference the bug in it).

Anton, could you please file a bug with Intel for this problem (using
your Premier Support account at http://premier.intel.com) and copy the
Intel bug link into the Jira issue for reference?

Martin