From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16779 invoked by alias); 9 Apr 2002 13:24:10 -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 16772 invoked from network); 9 Apr 2002 13:24:09 -0000 Received: from unknown (HELO pizda.ninka.net) (216.101.162.242) by sources.redhat.com with SMTP; 9 Apr 2002 13:24:09 -0000 Received: from localhost (IDENT:davem@localhost.localdomain [127.0.0.1]) by pizda.ninka.net (8.9.3/8.9.3) with ESMTP id GAA09900; Tue, 9 Apr 2002 06:15:53 -0700 Date: Tue, 09 Apr 2002 06:24:00 -0000 Message-Id: <20020409.061552.77173492.davem@redhat.com> To: matzmich@cs.tu-berlin.de Cc: gcc@gcc.gnu.org Subject: Re: Undocumented anomaly with EXTRA_CONSTRAINTS From: "David S. Miller" In-Reply-To: References: <20020409.050715.75514317.davem@redhat.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00341.txt.bz2 From: Michael Matz Date: Tue, 9 Apr 2002 15:14:43 +0200 (MET DST) I'm not quite sure what this has to do with only EXTRA_CONSTRAINT. Any 'm' constraint accepts pseudos before reload and unassigned pseudos while reloading. Exactly because unassigned pseudos _are_ memory slots. Where is this documented? :-) That's the point of my entire email. If all one did was read md.texi, upon implementing EXTRA_CONSTRAINT for MEM objects this issue would not be apparent until the compiler started to fail.