From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-268184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27927 invoked by alias); 1 Dec 2008 15:16:54 -0000
Received: (qmail 23420 invoked by uid 48); 1 Dec 2008 15:15:28 -0000
Date: Mon, 01 Dec 2008 15:16:00 -0000
Subject: [Bug target/38350]  New: odd extra unused stack space/register allocated with asm
X-Bugzilla-Reason: CC
Message-ID: <bug-38350-507@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2008-12/txt/msg00062.txt.bz2

For the attached code, there's no reason why the generated code at -O2 would
need an unused stack-slot (a second with -march=v10, a first with -march=v32)
when operand 5 (the last) of the asm is "g" than if it's "X".  Using "X" seems
a little awkward life-time-wise because the input is supposed to be valid.
I don't see this oddness on the host with native 4.1.2 on the host,
with/without -m32.


-- 
           Summary: odd extra unused stack space/register allocated with asm
           Product: gcc
           Version: 4.3.3
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: target
        AssignedTo: hp at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: cris-axis-elf


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38350