public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Geoff Keating <geoffk@redhat.com>
Cc: "kenner@vlsi1.ultra.nyu.edu" <kenner@vlsi1.ultra.nyu.edu>,
	"jh@suse.cz" <jh@suse.cz>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: simplify_subreg issues
Date: Mon, 11 Jun 2001 21:40:00 -0000	[thread overview]
Message-ID: <212030000.992320776@gandalf.codesourcery.com> (raw)
In-Reply-To: <200106120256.TAA04600@geoffk.org>

> The underlying problem is that 'volatile' doesn't make sense in
> conjunction with 'complex'.  We can't do complex loads or stores.  So,
> actually in this case the optimisation would be correct, because what
> we want to have is
>
> (set (mem/v:SF ...) ...)
>

I don't really understand what we do with `volatile' on a structure
type, in general, or what the standard says we have to do.

I guess one would like to avoid `f(y)' -- where `y' is some
volatile complex type -- generating more than one reference to any
word in `y'.

Are you saying that the use of `MEM_VOLATILE_P' is unncessary here,
or that the MEM should nont be volatile, or that the MEM_VOLATILE_P
test should be done only in conjuction with some additional check
that says `and is not a complex type'?

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

  reply	other threads:[~2001-06-11 21:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 19:10 Mark Mitchell
2001-06-11 19:40 ` Geoff Keating
2001-06-11 21:40   ` Mark Mitchell [this message]
2001-06-12  1:15     ` Geoff Keating
2001-06-12  1:35       ` Mark Mitchell
2001-06-12  2:46         ` Jan Hubicka
2001-06-12  2:52         ` Jan Hubicka
2001-06-12  3:09         ` Jan Hubicka
2001-06-12  3:51           ` Mark Mitchell
2001-06-12  9:15         ` Geoff Keating
2001-06-12  9:26           ` Jan Hubicka
2001-06-19 22:05           ` Mark Mitchell
2001-06-19 22:31             ` Geoff Keating
2001-06-12  2:27   ` Florian Weimer
2001-06-12  9:13   ` Carlo Wood
2001-06-12 10:35     ` Jose Eugenio Marchesi
2001-06-12  2:05 ` Jan Hubicka
2001-06-12  2:22 Richard Kenner
2001-06-12  9:16 ` Carlo Wood
2001-06-12  3:24 Richard Kenner

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=212030000.992320776@gandalf.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@redhat.com \
    --cc=jh@suse.cz \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).