This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [v3] libstdc++ vs. icc 8.1
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, judy dot ward at intel dot com, Andrew Pinski <pinskia at physics dot uc dot edu>
- Date: Tue, 6 Apr 2004 23:46:39 -0400
- Subject: Re: [v3] libstdc++ vs. icc 8.1
- References: <20040406223815.7810fea6.bkoz@redhat.com>
On Apr 6, 2004, at 23:38, Benjamin Kosnik wrote:
These fixups allow libstdc++ to be (almost) compiled by pre-released
versions of icc.
There are additional fixups that are necessary for some of the
libstdc++
testsuite files, but most are ok as-is. If somebody wants to fix the
problem test files up, I'm interested in applying the patch, and will
provide more details.
This patch is queued for gcc-3.4.1.
tested x86/linux g++
tested x86/linux icc 8.1 20040327Z
I have a question why should we put in workarounds in libstdc++ for ICC
at all.
Because if someone compiled their C++ code with our libstdc++ and ICC,
their
code needs to be licensed under the GPL as libstdc++ is licensed under
GPL+exception.
Also is the "workarounds" needed for libstdc++ to be standard C++ or
just for ICC to
compile them, if the later I would say we should not be doing this as
it clutters up
libstdc++. Also what about putting in "workarounds" to compile
libstdc++ with XLC
then as we should treat commercial compilers the same.
Just some thoughts,
Andrew Pinski