From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28064 invoked by alias); 29 Mar 2012 14:50:47 -0000 Received: (qmail 28036 invoked by uid 22791); 29 Mar 2012 14:50:46 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_NUMERIC_HELO,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 29 Mar 2012 14:50:33 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SDGgH-000885-6o for gcc@gcc.gnu.org; Thu, 29 Mar 2012 16:50:29 +0200 Received: from 193.128.72.68 ([193.128.72.68]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2012 16:50:29 +0200 Received: from paulo by 193.128.72.68 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 29 Mar 2012 16:50:29 +0200 To: gcc@gcc.gnu.org From: "Paulo J. Matos" Subject: unwind and type support in GCC47 Date: Thu, 29 Mar 2012 14:50:00 -0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: Pan/0.133 (House of Butterflies) X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2012-03/txt/msg00472.txt.bz2 Hi, I am porting my backend to GCC47 and have been jumping through some hurdles. libgcc is trying to compile unwind*.c files which I can't remember being there for GCC46. I deduce this files have to do with exception support GCC47 seems to want to make exceptions mandatory even though my backend doesn't really 'support' them (in the sense that our tests don't care about them). unwind*.c have a lot of variable definitions to mode SI as being a word, However, in my case a word is actually in mode QI (16bits). Is there anything I can do to stop libgcc from trying to compile these files or to make unwind compatible with my backend besides going blindly changing SI mode in variable declaration to QI mode? Cheers, -- PMatos