From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18607 invoked by alias); 31 Mar 2003 07:46:02 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 18593 invoked by uid 71); 31 Mar 2003 07:46:01 -0000 Date: Mon, 31 Mar 2003 08:56:00 -0000 Message-ID: <20030331074601.18592.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Eric Botcazou Subject: Re: target/6882: [SPARC] Useless stack adjustment code Reply-To: Eric Botcazou X-SW-Source: 2003-03/txt/msg02091.txt.bz2 List-Id: The following reply was made to PR target/6882; it has been noted by GNATS. From: Eric Botcazou To: Hans-Peter Nilsson Cc: , , , Subject: Re: target/6882: [SPARC] Useless stack adjustment code Date: Mon, 31 Mar 2003 09:37:25 +0200 > No, it seems a valid optimization request to not emit the > stack-adjustment code. Could you find a *specific* reason for > the stack-adjustment code? (Please state that in the PR.) No, I don't see a "specific" reason. But: - functions from the same translation unit that call it (and that appear after it in normal mode, but the restriction is lifted with -funit-at-a-time) don't actually emit the call, - would the benefit be worth it in real life, given that the costly operation is to call the function itself (for nothing)? I think the real optimization is not to emit the call at all. -- Eric Botcazou