From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15688 invoked by alias); 27 Jan 2008 19:54:46 -0000 Received: (qmail 15591 invoked by uid 48); 27 Jan 2008 19:54:02 -0000 Date: Sun, 27 Jan 2008 20:48:00 -0000 Message-ID: <20080127195402.15588.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/26099] support for type traits is not available In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "ghazi at gcc dot gnu dot org" 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-01/txt/msg03364.txt.bz2 ------- Comment #18 from ghazi at gcc dot gnu dot org 2008-01-27 19:54 ------- (In reply to comment #17) > Hi Kaveh. One problem I can see is that we are dealing with special member > functions, like constructors and assignment operators Ah, I guess you can't make those static. > Can you see anything > wrong with the straightforward implementation of idea per the attached > patchlet? If it looks ok to you, it would be matter of doing the same for the > other 2 files... It looks like you reversed the checks for the problematic cases when you see __PIC__. I wonder whether this will work on darwin which still binds locally for pic code. http://gcc.gnu.org/ml/gcc-patches/2008-01/msg00495.html The regtester might barf on this change, I don't have darwin to check. If it does, maybe instead you simply nuke the problematic cases when you see __PIC__. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26099