From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29271 invoked by alias); 30 Jun 2011 17:21:50 -0000 Received: (qmail 29232 invoked by uid 22791); 30 Jun 2011 17:21:49 -0000 X-SWARE-Spam-Status: No, hits=-6.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Jun 2011 17:21:31 +0000 Received: from int-mx01.intmail.prod.int.phx2.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p5UHLVeq027250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 30 Jun 2011 13:21:31 -0400 Received: from anchor.twiddle.net (vpn-224-214.phx2.redhat.com [10.3.224.214]) by int-mx01.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p5UHLU7Z011479; Thu, 30 Jun 2011 13:21:30 -0400 Message-ID: <4E0CB09A.90401@redhat.com> Date: Thu, 30 Jun 2011 17:41:00 -0000 From: Richard Henderson User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Thunderbird/3.1.10 MIME-Version: 1.0 To: Steven Bosscher CC: gcc-patches@gcc.gnu.org Subject: Re: [PATCH 04/12] vax: Emit prologue as rtl. References: <1309384152-25027-1-git-send-email-rth@redhat.com> <1309384152-25027-5-git-send-email-rth@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg02381.txt.bz2 On 06/29/2011 04:01 PM, Steven Bosscher wrote: > How many TARGET_ASM_FUNCTION_{PRO,EPI}LOGUE targets are left anyway? Answering the question that it sounds like you actually asked: 2 or 3. Not that it does us that much good because of the other uses. FWIW, Alpha appears to be the only target that (ab)uses ASM_DECLARE_FUNCTION_NAME to output unwind info. That might have been a mistake, considering the interference that causes with using elfos.h. I'm not sure what all the zeroing of backend variables that several targets are doing is for. Better GC at the end of the function maybe? r~ ---------------------- Users of TARGET_ASM_FUNCTION_PROLOGUE Outputs the real prologue pdp11 rs6000 if !TARGET_SCHED_PROLOG Outputs assembly comments arm m32r mep picochip rx Outputs unwind info ia64 (.regstk, .prologue) microblaze (.ent, .frame, .mask) mips (.ent, .frame, .mask) pa (.PROC and .CALLINFO) score (.ent, .frame, .mask) Other frv renaming of gr3?, frv_pack_insns mips mips16 function stub, gp load at function start microblaze add _interrupt_handler alias? mmix init register renaming? rs6000 emit .extern as needed before uses? sparc emit .register as needed Users of TARGET_ASM_FUNCTION_EPILOGUE Outputs the real epilogue arm thumb1 only pdp11 rs6000 if !TARGET_SCHED_PROLOG Outputs assembly comments picochip mmix actually just a newline? Outputs unwind info microblaze (.end) mips (.end) pa (.PROCEND and stuff) rs6000 aix traceback table score (.end) Other arm validate some frame offsets? frv reset variables i386 undo pic register renaming, darwin nop hack ia64 undo register renaming m32r reset variables microblaze finish _interrupt_handler alias, reset variables mips undo pic register renaming rs6000 darwin branch islands sh reset variables sparc unwind nop, deferred case vectors xtensa reset variables