From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20772 invoked by alias); 12 Dec 2008 18:43:14 -0000 Received: (qmail 18417 invoked by alias); 12 Dec 2008 18:41:52 -0000 Date: Fri, 12 Dec 2008 18:43:00 -0000 Message-ID: <20081212184152.18416.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug testsuite/35677] Intermitent failure "FAIL: libgomp.fortran/crayptr2.f90" In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dave at hiauly1 dot hia dot nrc dot ca" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-12/txt/msg01357.txt.bz2 ------- Comment #20 from dave at hiauly1 dot hia dot nrc dot ca 2008-12-12 18:41 ------- Subject: Re: Intermitent failure "FAIL: libgomp.fortran/crayptr2.f90" > Well, they are phasing it out in the long run perhaps but Apple is just > transitioning to gcc 4.2.1 at the moment so gcc will be in use for awhile > yet on darwin. I am unclear on what the clang/llvm will use for its libgcc > equivalent. Perhaps Chris Lattner can enlighten us on that. In principle, users can install libgcc* wherever they like. I think the install path for shared libraries is hardcoded in executables (otool -L). There's also DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH. As far as I know, the libgcc libraries shipped with 4.3 and in 4.4 are backwards compatible with earlier versions. My impression is that this issue is not confined to libgcc. The same problem is present for all the libraries provided by gcc. Any added features are going to make the new version incompatible with the system version, irrespective of ABI changes. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35677