From debbugs-submit-bounces@debbugs.gnu.org Thu Oct 20 08:05:06 2011 Received: (at submit) by debbugs.gnu.org; 20 Oct 2011 12:05:06 +0000 Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1RGrMu-0000oO-KW for submit@debbugs.gnu.org; Thu, 20 Oct 2011 08:05:06 -0400 Received: from eggs.gnu.org ([140.186.70.92]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1RGrMq-0000ns-DJ for submit@debbugs.gnu.org; Thu, 20 Oct 2011 08:05:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RGrLe-0003KM-1a for submit@debbugs.gnu.org; Thu, 20 Oct 2011 08:03:47 -0400 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, RP_MATCHES_RCVD,T_DKIM_INVALID autolearn=unavailable version=3.3.1 Received: from lists.gnu.org ([140.186.70.17]:42292) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGrLd-0003K1-V7 for submit@debbugs.gnu.org; Thu, 20 Oct 2011 08:03:45 -0400 Received: from eggs.gnu.org ([140.186.70.92]:40176) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGrLX-0001Mi-No for bug-libtool@gnu.org; Thu, 20 Oct 2011 08:03:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RGrLR-00031F-8x for bug-libtool@gnu.org; Thu, 20 Oct 2011 08:03:39 -0400 Received: from rcdn-iport-9.cisco.com ([173.37.86.80]:3540) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RGrLR-0002zF-20 for bug-libtool@gnu.org; Thu, 20 Oct 2011 08:03:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jsquyres@cisco.com; l=3665; q=dns/txt; s=iport; t=1319112213; x=1320321813; h=mime-version:subject:from:date:cc: content-transfer-encoding:message-id:references:to; bh=WquXa2HHZgWkNvGUnbfTzI4NeNM9SAbr1QBj362soWE=; b=dX7ozCY8ui2WayH1hMaooKJcvzGLW/yDTryjdL6z/WGFslUoocSz/nip rUFpZ2CjPpVfOOCQbv9IU6CNITpd/YsECtXIEzkLS7v8kk4Lc8XwvoSwC Ma2XcS8OW0SJV60tcUgsdWQnbfGRvvtQxKmV9eAfFxeWJSqtuD5NWJfIy 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMFANINoE6tJV2b/2dsb2JhbAApFwOmVYJBgQWBbgEBAQMBAQIPAQUiPwULHAMBAgEuKB4HAggZFA6HXggklngBnjmFFII0YQSRZoIakXM X-IronPort-AV: E=Sophos;i="4.69,379,1315180800"; d="scan'208";a="29768985" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 20 Oct 2011 12:03:31 +0000 Received: from rtp-jsquyres-8917.cisco.com (rtp-jsquyres-8917.cisco.com [10.117.133.232]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p9KC3YrG025088; Thu, 20 Oct 2011 12:03:34 GMT Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1084) Subject: Fwd: [OMPI devel] make check fails for Intel 2011.6.233 (OpenMPI 1.4.3) From: Jeff Squyres Date: Thu, 20 Oct 2011 08:03:30 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <7ADEDF69-02C2-4A99-A78B-C1A16EF0D44F@cisco.com> References: To: bug-libtool@gnu.org X-Mailer: Apple Mail (2.1084) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.17 X-Spam-Score: -5.3 (-----) X-Debbugs-Envelope-To: submit Cc: Larry Baker X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: debbugs-submit-bounces@debbugs.gnu.org Errors-To: debbugs-submit-bounces@debbugs.gnu.org X-Spam-Score: -5.4 (-----) Libtool developers -- FYI. I don't know offhand if you're checking the intel compiler = #defines for version numbers, but the following issue just came up on = the Open MPI list: the intel 12.1.x compilers seem to have done terrible = things to the version #defines. So we're passing along this info in = case you need it. See below. Begin forwarded message: > From: Larry Baker > Date: October 19, 2011 4:25:26 PM EDT > To: Open MPI Developers > Subject: Re: [OMPI devel] make check fails for Intel 2011.6.233 = (OpenMPI 1.4.3) > Reply-To: Open MPI Developers >=20 > Here's what I get for the version no. macros from the Intel compilers = I have installed on our cluster: >=20 >> Intel V11.1.080 >>=20 >> $ icc -v >> Version 11.1=20 >>=20 >> #define __ICC 1110 >> #define __INTEL_COMPILER 1110 >> #define __INTEL_COMPILER_BUILD_DATE 20101201 >>=20 >> Intel V2011.3.174 >>=20 >> $ icc -v >> Version 12.0.3 >>=20 >> #define __ICC 1200 >> #define __INTEL_COMPILER 1200 >> #define __INTEL_COMPILER_BUILD_DATE 20110309 >>=20 >> Intel V2011.4.191 >>=20 >> $ icc -v >> Version 12.0.4 >>=20 >> #define __ICC 1200 >> #define __INTEL_COMPILER 1200 >> #define __INTEL_COMPILER_BUILD_DATE 20110427 >>=20 >> Intel V2011.5.220 >>=20 >> $ icc -v >> Version 12.0.5 >>=20 >> #define __ICC 1200 >> #define __INTEL_COMPILER 1200 >> #define __INTEL_COMPILER_BUILD_DATE 20110719 >>=20 >> Intel V2011.6.233 >>=20 >> $ icc -v >> icc version 12.1.0 (gcc version 4.1.2 compatibility) >>=20 >> #define __ICC 9999 >> #define __INTEL_COMPILER 9999 >> #define __INTEL_COMPILER_BUILD_DATE 20110811 >=20 > As Hubert mentioned, only the build date has a reliable value. >=20 > Larry Baker > US Geological Survey > 650-329-5608 > baker@usgs.gov >=20 > On 19 Oct 2011, at 11:45 AM, Larry Baker wrote: >=20 >> I posted my findings about the bad version no. macros to the same = thread that described the Intel V12.1 optimizer bug = (http://software.intel.com/en-us/forums/showthread.php?t=3D87132). The = response I got is: >>=20 >>> Posted By: Hubert Haberstock (Intel) >>> __________________________________________ >>>=20 >>> The build date is currently the only suitable macro. This allows to = check for the Intel Compiler and for specific compiler versions. Makes = sense? Regards, Hubert. >>> __________________________________________ >>=20 >> That is contrary to what the online V12.1 documentation says. I'm = going to find out what the previous versions do, then report this = through my normal support channels. If the documentation is wrong, they = should fix it; if the documentation is right, they should fix the = compiler. (However, there will still be an errant V12.1.0 that reports = itself as 9999, so use of the version no. macros will never be reliable = without a hack to handle this errant case.) I'll report here what I = find about the values of the version no. macros. It is probably better, = though, that automake/libtool rely on the output of icc -v, since that = seems to always result in a value that matches the version of the = product (as opposed to #define __INTEL_COMPILER 9999 and #define __ICC = 9999 from within the V12.1.0 compiler). >>=20 >> Larry Baker >> US Geological Survey >> 650-329-5608 >> baker@usgs.gov If you care, you can see the rest of the thread here: http://www.open-mpi.org/community/lists/devel/2011/10/9791.php --=20 Jeff Squyres jsquyres@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ From debbugs-submit-bounces@debbugs.gnu.org Tue Nov 08 14:17:55 2011 Received: (at submit) by debbugs.gnu.org; 8 Nov 2011 19:17:55 +0000 Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1RNrBC-0003s4-8P for submit@debbugs.gnu.org; Tue, 08 Nov 2011 14:17:55 -0500 Received: from eggs.gnu.org ([140.186.70.92]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1RNr3h-0003fo-7A for submit@debbugs.gnu.org; Tue, 08 Nov 2011 14:10:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RNr3Z-0007wk-NO for submit@debbugs.gnu.org; Tue, 08 Nov 2011 14:10:03 -0500 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on eggs.gnu.org X-Spam-Level: X-Spam-Status: No, score=-5.4 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD autolearn=unavailable version=3.3.1 Received: from lists.gnu.org ([140.186.70.17]:46981) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNr3Z-0007wa-Ka for submit@debbugs.gnu.org; Tue, 08 Nov 2011 14:10:01 -0500 Received: from eggs.gnu.org ([140.186.70.92]:45292) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNr3X-0002FE-Tt for bug-libtool@gnu.org; Tue, 08 Nov 2011 14:10:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RNr3V-0007vt-TR for bug-libtool@gnu.org; Tue, 08 Nov 2011 14:09:59 -0500 Received: from gscamnlh01.wr.usgs.gov ([130.118.9.68]:43127) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNr3V-0007th-Av for bug-libtool@gnu.org; Tue, 08 Nov 2011 14:09:57 -0500 Received: from savaii.wr.usgs.gov ([130.118.45.7]) by gscamnlh01.wr.usgs.gov (Lotus Domino Release 8.5.2FP2HF661) with ESMTP id 2011110811095462-161108 ; Tue, 8 Nov 2011 11:09:54 -0800 Message-Id: <96735770-EA4B-4C63-8DCD-1139879802AC@usgs.gov> From: Larry Baker To: bug-libtool@gnu.org In-Reply-To: <7ADEDF69-02C2-4A99-A78B-C1A16EF0D44F@cisco.com> Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: [OMPI devel] make check fails for Intel 2011.6.233 (OpenMPI 1.4.3) Date: Tue, 8 Nov 2011 11:09:54 -0800 References: <7ADEDF69-02C2-4A99-A78B-C1A16EF0D44F@cisco.com> X-Mailer: Apple Mail (2.936) X-MIMETrack: Itemize by SMTP Server on gscamnlh01/SERVER/USGS/DOI(Release 8.5.2FP2HF661 | September 20, 2011) at 11/08/2011 11:09:54, Serialize by Router on gscamnlh01/SERVER/USGS/DOI(Release 8.5.2FP2HF661 | September 20, 2011) at 11/08/2011 11:09:57, Serialize complete at 11/08/2011 11:09:57 Content-Type: multipart/alternative; boundary=Apple-Mail-17-1022295000 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.17 X-Spam-Score: -6.6 (------) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Tue, 08 Nov 2011 14:17:53 -0500 Cc: Jeff Squyres X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: debbugs-submit-bounces@debbugs.gnu.org Errors-To: debbugs-submit-bounces@debbugs.gnu.org X-Spam-Score: -6.6 (------) --Apple-Mail-17-1022295000 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes FYI. This is a follow-up to Jeff Squyres' earlier note. Intel release 2011.6.233 has a bug in the vectorizer that breaks OpenMPI. The bug is fixed in Intel release 2011.7.256. Both Intel release 2011.6.233 and 2011.7.256 identify themselves as V12.1.0 using the -v command line option. (This bug has been reported.) The only reliable way to distinguish the Intel compiler release is the predefined __INTEL_COMPILER_BUILD_DATE macro. Below are the compiler identification strings available from the Intel 2011.6.233 and 2011.7.256 compiler releases: > [baker@hydra tmp]$ module list > Currently Loaded Modulefiles: > 1) modules 2) compilers/intel/2011.6.233 > [baker@hydra tmp]$ icc -v > icc version 12.1.0 (gcc version 4.1.2 compatibility) > [baker@hydra tmp]$ icc -E -dM junk.c | grep INTEL > #define __INTEL_COMPILER 9999 > #define __INTEL_RTTI__ 1 > #define __INTEL_COMPILER_BUILD_DATE 20110811 > [baker@hydra tmp]$ module list > Currently Loaded Modulefiles: > 1) modules 2) compilers/intel/2011.7.256 > [baker@hydra tmp]$ icc -v > icc version 12.1.0 (gcc version 4.1.2 compatibility) > [baker@hydra tmp]$ icc -E -dM junk.c | grep INTEL > #define __INTEL_COMPILER 1210 > #define __INTEL_RTTI__ 1 > #define __INTEL_COMPILER_BUILD_DATE 20111011 Larry Baker US Geological Survey 650-329-5608 baker@usgs.gov On 20 Oct 2011, at 5:03 AM, Jeff Squyres wrote: > Libtool developers -- > > FYI. I don't know offhand if you're checking the intel compiler > #defines for version numbers, but the following issue just came up > on the Open MPI list: the intel 12.1.x compilers seem to have done > terrible things to the version #defines. So we're passing along > this info in case you need it. > > See below. > > Begin forwarded message: > >> From: Larry Baker >> Date: October 19, 2011 4:25:26 PM EDT >> To: Open MPI Developers >> Subject: Re: [OMPI devel] make check fails for Intel 2011.6.233 >> (OpenMPI 1.4.3) >> Reply-To: Open MPI Developers >> >> Here's what I get for the version no. macros from the Intel >> compilers I have installed on our cluster: >> >>> Intel V11.1.080 >>> >>> $ icc -v >>> Version 11.1 >>> >>> #define __ICC 1110 >>> #define __INTEL_COMPILER 1110 >>> #define __INTEL_COMPILER_BUILD_DATE 20101201 >>> >>> Intel V2011.3.174 >>> >>> $ icc -v >>> Version 12.0.3 >>> >>> #define __ICC 1200 >>> #define __INTEL_COMPILER 1200 >>> #define __INTEL_COMPILER_BUILD_DATE 20110309 >>> >>> Intel V2011.4.191 >>> >>> $ icc -v >>> Version 12.0.4 >>> >>> #define __ICC 1200 >>> #define __INTEL_COMPILER 1200 >>> #define __INTEL_COMPILER_BUILD_DATE 20110427 >>> >>> Intel V2011.5.220 >>> >>> $ icc -v >>> Version 12.0.5 >>> >>> #define __ICC 1200 >>> #define __INTEL_COMPILER 1200 >>> #define __INTEL_COMPILER_BUILD_DATE 20110719 >>> >>> Intel V2011.6.233 >>> >>> $ icc -v >>> icc version 12.1.0 (gcc version 4.1.2 compatibility) >>> >>> #define __ICC 9999 >>> #define __INTEL_COMPILER 9999 >>> #define __INTEL_COMPILER_BUILD_DATE 20110811 >> >> As Hubert mentioned, only the build date has a reliable value. >> >> Larry Baker >> US Geological Survey >> 650-329-5608 >> baker@usgs.gov >> >> On 19 Oct 2011, at 11:45 AM, Larry Baker wrote: >> >>> I posted my findings about the bad version no. macros to the same >>> thread that described the Intel V12.1 optimizer bug (http://software.intel.com/en-us/forums/showthread.php?t=87132 >>> ). The response I got is: >>> >>>> Posted By: Hubert Haberstock (Intel) >>>> __________________________________________ >>>> >>>> The build date is currently the only suitable macro. This allows >>>> to check for the Intel Compiler and for specific compiler >>>> versions. Makes sense? Regards, Hubert. >>>> __________________________________________ >>> >>> That is contrary to what the online V12.1 documentation says. I'm >>> going to find out what the previous versions do, then report this >>> through my normal support channels. If the documentation is >>> wrong, they should fix it; if the documentation is right, they >>> should fix the compiler. (However, there will still be an errant >>> V12.1.0 that reports itself as 9999, so use of the version no. >>> macros will never be reliable without a hack to handle this errant >>> case.) I'll report here what I find about the values of the >>> version no. macros. It is probably better, though, that automake/ >>> libtool rely on the output of icc -v, since that seems to always >>> result in a value that matches the version of the product (as >>> opposed to #define __INTEL_COMPILER 9999 and #define __ICC 9999 >>> from within the V12.1.0 compiler). >>> >>> Larry Baker >>> US Geological Survey >>> 650-329-5608 >>> baker@usgs.gov > > If you care, you can see the rest of the thread here: > > http://www.open-mpi.org/community/lists/devel/2011/10/9791.php > > -- > Jeff Squyres > jsquyres@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > --Apple-Mail-17-1022295000 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=US-ASCII FYI.  This is a follow-up = to Jeff Squyres' earlier note.

Intel release = 2011.6.233 has a bug in the vectorizer that breaks OpenMPI.  The = bug is fixed in Intel release = 2011.7.256.

Both Intel release 2011.6.233 and = 2011.7.256 identify themselves as V12.1.0 using the -v command line = option.  (This bug has been reported.)

The = only reliable way to distinguish the Intel compiler release is = the predefined __INTEL_COMPILER_BUILD_DATE = macro.

Below are the compiler identification = strings available from the Intel 2011.6.233 and 2011.7.256 compiler = releases:

[baker@hydra tmp]$ module = list          
Currently Loaded = Modulefiles:
  1) modules           =            2) = compilers/intel/2011.6.233

[baker@hydra tmp]$ icc -v
icc version 12.1.0 (gcc = version 4.1.2 = compatibility)

[baker@hydra tmp]$ icc -E -dM junk.c | grep = INTEL
#define __INTEL_COMPILER 9999
#define __INTEL_RTTI__ = 1
#define __INTEL_COMPILER_BUILD_DATE = 20110811

[baker@hydra tmp]$ module list
Currently Loaded = Modulefiles:
  1) modules           =            2) = compilers/intel/2011.7.256

[baker@hydra tmp]$ icc -v
icc version 12.1.0 (gcc = version 4.1.2 = compatibility)

[baker@hydra tmp]$ icc -E -dM junk.c | grep = INTEL
#define __INTEL_COMPILER 1210
#define __INTEL_RTTI__ = 1
#define __INTEL_COMPILER_BUILD_DATE = 20111011

Larry = Baker
US Geological Survey
650-329-5608
<= /div>

On 20 Oct = 2011, at 5:03 AM, Jeff Squyres wrote:

Libtool= developers --

FYI.  I don't know offhand if you're checking = the intel compiler #defines for version numbers, but the following issue = just came up on the Open MPI list: the intel 12.1.x compilers seem to = have done terrible things to the version #defines.  So we're = passing along this info in case you need it.

See = below.

Begin forwarded message:

From: Larry Baker <baker@usgs.gov>
Date: October 19, 2011 4:25:26 PM = EDT
To: Open MPI Developers = <devel@open-mpi.org>
Subject: Re: [OMPI devel] make check fails = for Intel 2011.6.233 (OpenMPI 1.4.3)
Reply-To: Open MPI Developers <devel@open-mpi.org>

Here's what I get for the version no. macros from the = Intel compilers I have installed on our = cluster:

Intel V11.1.080

$ icc = -v
Version 11.1

#define __ICC = 1110
#define __INTEL_COMPILER = 1110
#define __INTEL_COMPILER_BUILD_DATE = 20101201

Intel = V2011.3.174

$ icc = -v
Version 12.0.3

#define __ICC = 1200
#define __INTEL_COMPILER = 1200
#define __INTEL_COMPILER_BUILD_DATE = 20110309

Intel = V2011.4.191

$ icc = -v
Version 12.0.4

#define __ICC = 1200
#define __INTEL_COMPILER = 1200
#define __INTEL_COMPILER_BUILD_DATE = 20110427

Intel = V2011.5.220

$ icc = -v
Version 12.0.5

#define __ICC = 1200
#define __INTEL_COMPILER = 1200
#define __INTEL_COMPILER_BUILD_DATE = 20110719

Intel = V2011.6.233

$ icc = -v
icc version 12.1.0 (gcc version 4.1.2 = compatibility)

#define __ICC = 9999
#define __INTEL_COMPILER = 9999
#define __INTEL_COMPILER_BUILD_DATE = 20110811

As Hubert = mentioned, only the build date has a reliable = value.

Larry = Baker
US Geological = Survey
650-329-5608
baker@usgs.gov

On 19 Oct = 2011, at 11:45 AM, Larry Baker wrote:

I posted my findings about the bad version no. macros to = the same thread that described the Intel V12.1 optimizer bug (h= ttp://software.intel.com/en-us/forums/showthread.php?t=3D87132). =  The response I got is:

Posted = By: Hubert Haberstock = (Intel)
__________________________________________
<= /blockquote>

The = build date is currently the only suitable macro. This allows to check = for the Intel Compiler and for specific compiler versions. Makes sense? = Regards, Hubert.
__________________________________________
<= /blockquote>

That is contrary to what the = online V12.1 documentation says.  I'm going to find out what the = previous versions do, then report this through my normal support = channels.  If the documentation is wrong, they should fix it; if = the documentation is right, they should fix the compiler. =  (However, there will still be an errant V12.1.0 that reports = itself as 9999, so use of the version no. macros will never be reliable = without a hack to handle this errant case.)  I'll report here what = I find about the values of the version no. macros.  It is probably = better, though, that automake/libtool rely on the output of icc -v, = since that seems to always result in a value that matches the version of = the product (as opposed to #define __INTEL_COMPILER 9999 and #define = __ICC 9999 from within the V12.1.0 = compiler).

Larry = Baker
US Geological = Survey
650-329-5608
baker@usgs.gov

If you care, you can see the rest of the thread here:

=    ht= tp://www.open-mpi.org/community/lists/devel/2011/10/9791.php

--=
Jeff Squyres
jsquyres@cisco.com
For = corporate legal information go = to:
http://www.cisco.com/web/about/doing_business/legal/cri/


= --Apple-Mail-17-1022295000-- From debbugs-submit-bounces@debbugs.gnu.org Tue Jun 17 11:45:46 2025 Received: (at 9806) by debbugs.gnu.org; 17 Jun 2025 15:45:46 +0000 Received: from localhost ([127.0.0.1]:60774 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1uRYVN-0000Tm-8s for submit@debbugs.gnu.org; Tue, 17 Jun 2025 11:45:46 -0400 Received: from smtp-out2.mpia-hd.mpg.de ([149.217.70.16]:24955) by debbugs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1uRVXm-0005CV-NW for 9806@debbugs.gnu.org; Tue, 17 Jun 2025 08:36:07 -0400 Received: from mailer.mpia-hd.mpg.de (mailer.mpia-hd.mpg.de [149.217.71.6]) by smtp-out2.mpia-hd.mpg.de (Postfix) with ESMTPS id A3F08139D1 for <9806@debbugs.gnu.org>; Tue, 17 Jun 2025 14:35:55 +0200 (CEST) Received: from mailer.mpia-hd.mpg.de (localhost [127.0.0.1]) by mailer.mpia-hd.mpg.de (Postfix) with ESMTP id 957C910C6E76 for <9806@debbugs.gnu.org>; Tue, 17 Jun 2025 14:35:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mpia-hd.mpg.de; h=content-disposition:content-type:content-type:mime-version :reply-to:message-id:subject:subject:from:from:date:date :received; s=mailer201911; t=1750163755; x=1751978156; bh=HPkoFA MIsCJWFyQT+gOpI2ArQGZIZi+w4YALKiaQe5c=; b=Zb7+zkLOHRR4+FB4pWAJEA YD0Iq1P9clQ8M6FCPQp+OKujoBPyGhfXn7DVCRreGCpByp9Xl+dUW0+sTL+YVFJQ fm4jK9xC5Fm2qUb/vwTJU+wlDeBidvDwk8HztS7YnwBLgFjKva5uzKRlNqvNaP7o N2xpgdWxooSG5Z/SPlQtq8dKledlD+LBXlwtu/9+S9GHKjFcejey+6FfWhHMUymC pmt82PXU1A4qgjuesk+3QoHqPvUUCTl6RaTq9rnrjutGygLZcS/nAN/snx5dvXuY U9cesN6Z2dX3Oc4W7lG6VUYILG2md3tVXx/EJyUHrEgNr/Av3X5Inb6KFV9YjMKA == X-Virus-Scanned: amavisd-new at mpia-hd.mpg.de Received: from mailer.mpia-hd.mpg.de (mailer.mpia-hd.mpg.de [149.217.71.6]) by mailer.mpia-hd.mpg.de (Postfix) with ESMTPSA id 633EB10C6E70 for <9806@debbugs.gnu.org>; Tue, 17 Jun 2025 14:35:55 +0200 (CEST) Date: Tue, 17 Jun 2025 14:35:50 +0200 From: "Richard J. Mathar" To: 9806@debbugs.gnu.org Subject: Fwd: [OMPI devel] make check fails for Intel 2011.6.233 (OpenMPI 1.4.3) Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 9806 X-Mailman-Approved-At: Tue, 17 Jun 2025 11:45:44 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: mathar@mpia-hd.mpg.de Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) For the Intel OneAPI compiler 2024.0 we have for comparison: mathar@mathar:~> /opt/apps/software/intel2024/oneapi/2024.0/bin/icx -E -dM t2.c | grep INTEL #define __INTEL_CLANG_COMPILER 20240002 #define __INTEL_LLVM_COMPILER 20240002 mathar@mathar:~> /opt/apps/software/intel2024/oneapi/2024.0/bin/icx -v Intel(R) oneAPI DPC++/C++ Compiler 2024.0.2 (2024.0.2.20231213) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /opt/apps/software/intel2024/oneapi/compiler/2024.0/bin/compiler Configuration file: /opt/apps/software/intel2024/oneapi/compiler/2024.0/bin/compiler/../icx.cfg Found candidate GCC installation: /usr/lib64/gcc/x86_64-suse-linux/7 Selected GCC installation: /usr/lib64/gcc/x86_64-suse-linux/7 Candidate multilib: .;@m64 Selected multilib: .;@m64