public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH] Fix handling of EXPAND_MEMORY for TFmode memory constraint in asm
@ 2012-12-01 22:46 John David Anglin
  2012-12-30 16:26 ` John David Anglin
  2013-01-02 18:17 ` Richard Henderson
  0 siblings, 2 replies; 3+ messages in thread
From: John David Anglin @ 2012-12-01 22:46 UTC (permalink / raw)
  To: gcc-patches

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  <dave.anglin@nrc-cnrc.gc.ca>

	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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-01-02 18:17 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-01 22:46 [PATCH] Fix handling of EXPAND_MEMORY for TFmode memory constraint in asm John David Anglin
2012-12-30 16:26 ` John David Anglin
2013-01-02 18:17 ` Richard Henderson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).