From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19185 invoked by alias); 3 Apr 2012 09:03:03 -0000 Received: (qmail 19157 invoked by uid 22791); 3 Apr 2012 09:03:02 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from mel.act-europe.fr (HELO mel.act-europe.fr) (194.98.77.210) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 03 Apr 2012 09:02:49 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-smtp.eu.adacore.com (Postfix) with ESMTP id 4A2F5290029; Tue, 3 Apr 2012 11:02:53 +0200 (CEST) Received: from mel.act-europe.fr ([127.0.0.1]) by localhost (smtp.eu.adacore.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edVAtK17jcRr; Tue, 3 Apr 2012 11:02:53 +0200 (CEST) Received: from [192.168.1.2] (bon31-6-88-161-99-133.fbx.proxad.net [88.161.99.133]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mel.act-europe.fr (Postfix) with ESMTP id C280129000D; Tue, 3 Apr 2012 11:02:52 +0200 (CEST) From: Eric Botcazou To: Richard Guenther Subject: Re: [PATCH] Dissociate store_expr's temp from exp so that it is not marked as addressable Date: Tue, 03 Apr 2012 09:03:00 -0000 User-Agent: KMail/1.9.9 Cc: Martin Jambor , GCC Patches References: <20120329232205.GB2817@virgil.arch.suse.de> <201204031001.50984.ebotcazou@adacore.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <201204031102.12177.ebotcazou@adacore.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-04/txt/msg00073.txt.bz2 > Yeah, that sounds reasonable. There is a further subtlety in the second temp allocation when the expression doesn't use the alias set of its type. In that case, we cannot pass the type to set_mem_attributes. In fact, since assign_stack_temp_for_type already calls the appropriate set_mem_* routines, the best thing to do might be to remove the call to set_mem_attributes altogether in that case. -- Eric Botcazou