From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30297 invoked by alias); 2 Dec 2003 05:49:25 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 30249 invoked from network); 2 Dec 2003 05:49:24 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 2 Dec 2003 05:49:24 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1AR3P4-0002oS-00; Tue, 02 Dec 2003 00:48:54 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 41DDA4B359; Tue, 2 Dec 2003 00:49:04 -0500 (EST) To: brobecker@gnat.com, drow@mvista.com Subject: Re: [RFA] OSF/1 - "next" over prologueless function call Cc: gdb-patches@sources.redhat.com Message-Id: <20031202054904.41DDA4B359@berman.michael-chastain.com> Date: Tue, 02 Dec 2003 05:49:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2003-12/txt/msg00040.txt.bz2 drow> But about the OSF/1 specific target hook: no, this should be an drow> Alpha-specific target hook instead. I agree with Daniel here. I have little expertise on 64-bit architectures, but I expect this would be a common optimization for architectures where there is a $gp or similar register which needs to be loaded at the beginning of each function, and a linker can figure out that $gp has the same value across many different functions. Michael C