From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16586 invoked by alias); 1 Dec 2012 22:46:24 -0000 Received: (qmail 16552 invoked by uid 22791); 1 Dec 2012 22:46:22 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from hiauly1.hia.nrc.ca (HELO hiauly1.hia.nrc.ca) (132.246.10.84) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 01 Dec 2012 22:46:13 +0000 Received: by hiauly1.hia.nrc.ca (Postfix, from userid 1000) id 3D5354CB8; Sat, 1 Dec 2012 17:46:09 -0500 (EST) Date: Sat, 01 Dec 2012 22:46:00 -0000 From: John David Anglin To: gcc-patches@gcc.gnu.org Subject: [PATCH] Fix handling of EXPAND_MEMORY for TFmode memory constraint in asm Message-ID: <20121201224609.GA18582@hiauly1.hia.nrc.ca> Reply-To: John David Anglin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) 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-12/txt/msg00042.txt.bz2 The attached change fixes the compilation of the following asm in libquadmath/math/fmaq.c: asm volatile ("" : : "m" (v.value)); The issue arises because there is no support for directly loading TFmode objects. Ok for trunk? Dave -- J. David Anglin dave.anglin@nrc-cnrc.gc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6602) 2012-12-01 John David Anglin PR middle-end/55198 * expr.c (expand_expr_real_1): Don't use bitfield extraction for non BLKmode objects when EXPAND_MEMORY is specified. Index: expr.c =================================================================== --- expr.c (revision 193685) +++ expr.c (working copy) @@ -9928,7 +9928,8 @@ && GET_MODE_CLASS (mode) != MODE_COMPLEX_INT && GET_MODE_CLASS (mode) != MODE_COMPLEX_FLOAT && modifier != EXPAND_CONST_ADDRESS - && modifier != EXPAND_INITIALIZER) + && modifier != EXPAND_INITIALIZER + && modifier != EXPAND_MEMORY) /* If the field is volatile, we always want an aligned access. Do this in following two situations: 1. the access is not already naturally