public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/5366: asm code produces an error without -O but is ok with -O
Date: Mon, 14 Jan 2002 18:26:00 -0000	[thread overview]
Message-ID: <20020115022601.1330.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/5366; it has been noted by GNATS.

From: Richard Henderson <rth@redhat.com>
To: erl-dev@altus.qc.ca
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: optimization/5366: asm code produces an error without -O but is ok with -O
Date: Mon, 14 Jan 2002 18:18:39 -0800

 On Sat, Jan 12, 2002 at 07:29:09PM -0500, erl-dev@altus.qc.ca wrote:
 > 	   __asm __volatile ("" : "=m" (lock->__status) : "0" (lock->__status));
 
 You needn't bother with the matching constraint, and that is
 in fact what leads to your troubles.
 
 The memory address is fully specified by lock->__status.  Since
 the same value is used on both sides, you know it is the same
 address, and thus using "=m" and "m" is sufficient.
 
 At -O0, the address calculations for the two structure references
 are not subject to common subexpression elimination, so the 
 register allocator cannot easily prove that the two addresses
 are the same, so it aborts.
 
 
 r~


             reply	other threads:[~2002-01-15  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14 18:26 Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-12 17:17 rodrigc
2002-01-12 16:36 erl-dev

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=20020115022601.1330.qmail@sources.redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).