From: John David Anglin <dave.anglin@bell.net>
To: John David Anglin <dave.anglin@nrc-cnrc.gc.ca>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix handling of EXPAND_MEMORY for TFmode memory constraint in asm
Date: Sun, 30 Dec 2012 16:26:00 -0000 [thread overview]
Message-ID: <BLU0-SMTP513F6D814E83AE8F7DA25973D0@phx.gbl> (raw)
In-Reply-To: <20121201224609.GA18582@hiauly1.hia.nrc.ca>
Ping.
On 1-Dec-12, at 5:46 PM, John David Anglin wrote:
> 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
>
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2012-12-30 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 22:46 John David Anglin
2012-12-30 16:26 ` John David Anglin [this message]
2013-01-02 18:17 ` Richard Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BLU0-SMTP513F6D814E83AE8F7DA25973D0@phx.gbl \
--to=dave.anglin@bell.net \
--cc=dave.anglin@nrc-cnrc.gc.ca \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).