From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32738 invoked by alias); 25 Feb 2003 14:17:29 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 32731 invoked from network); 25 Feb 2003 14:17:27 -0000 Received: from unknown (HELO mail.polimi.it) (131.175.12.67) by 172.16.49.205 with SMTP; 25 Feb 2003 14:17:27 -0000 Received: from burning-guy (paolob@burning-guy.rett.polimi.it [131.175.65.145]) by mail.polimi.it (Switch-2.2.4/Switch-2.2.4) with ESMTP id h1PEHN500047; Tue, 25 Feb 2003 15:17:23 +0100 (MET) Content-Type: text/plain; charset="us-ascii" From: Paolo Bonzini Reply-To: bonzini@gnu.org To: schwab@suse.de, gcc@gcc.gnu.org Subject: Re: GCC 3.3 release criteria Date: Tue, 25 Feb 2003 14:45:00 -0000 User-Agent: KMail/1.4.2 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200302251515.00467.paolo.bonzini@polimi.it> X-SW-Source: 2003-02/txt/msg01716.txt.bz2 > If you need a certain register, use __asm__("reg"). Everything else is > calling for trouble. I agree. Though for more control I'd like very much: - __asm__() or __attribute__(always_register) for putting a variable into=20 whatever register the compiler cares, but *in a register* - __asm__(regclass) which can be very handy for example for reserving a bra= nch=20 register on the IA64. --=20 |_ _ _ __ |_)(_)| ) ;'_.