From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18190 invoked by alias); 8 Nov 2014 20:29:28 -0000 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 Received: (qmail 18091 invoked by uid 48); 8 Nov 2014 20:29:23 -0000 From: "howarth at bromo dot med.uc.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libitm/63781] potential linkage issue with libitm.1.dylib Date: Sat, 08 Nov 2014 20:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libitm X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: howarth at bromo dot med.uc.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg00551.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63781 --- Comment #10 from howarth at bromo dot med.uc.edu --- (In reply to Iain Sandoe from comment #9) > (In reply to Francois-Xavier Coudert from comment #8) > > As far as I understand, libitm is supposed to be used with either C or C++. > > As such, it contains some C++ code which requires libstdc++, but doesn't > > link to it by default. That way, if someone compiles C code with libitm, it > > doesn't use need the C++ libitm code, and doesn't pull libstdc++. And when > > one compiles C++ code, libstdc++ is linked in anyway, so it's no problem. > > > > In short, I'm afraid I don't understand what you think the problem is :) > > Do you have a "real" testcase that fails to link? > > This is quite correct, as I pointed out to Jack before he opened the issue. > libitm weak links to the relevant symbols and uses them as required by the > final program. So the compiler will emit the ___cxa_tm_cleanup to resolve the undefined symbol in libitm?