public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fjahanian at apple dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/17884] New: asm 'volatile' is not honored as documented
Date: Thu, 07 Oct 2004 19:31:00 -0000	[thread overview]
Message-ID: <20041007193056.17884.fjahanian@apple.com> (raw)

In the following test case compiled with -O1 the add instruction is found *outside* the protective
"mtfsf". 'volatile' keyword added to 'asm' was meant to prevent such cases. gcc-3.3 behaves
correctly. Is this a know problem? Is there a PR already for it?

double foo( )
{
        double sum;
        double fpenv;
        double DDD, FFF;

        sum = DDD + FFF;
        asm volatile("mtfsf 255,%0" : : "f" (fpenv));
        return sum;
}

_foo:
        mtfsf 255,f0
        fadd f1,f1,f0
        blr

-- 
           Summary: asm 'volatile' is not honored as documented
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: fjahanian at apple dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: powerpc-apple-darwin7.2.0
  GCC host triplet: powerpc-apple-darwin7.2.0
GCC target triplet: powerpc-apple-darwin7.2.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17884


             reply	other threads:[~2004-10-07 19:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 19:31 fjahanian at apple dot com [this message]
2004-10-07 19:35 ` [Bug tree-optimization/17884] [4.0 Regression] " pinskia at gcc dot gnu dot org
2004-10-07 20:02 ` amacleod at redhat dot com
2004-10-07 20:37 ` fjahanian at apple dot com
2004-10-07 21:51 ` fjahanian at apple dot com
2004-10-07 22:02 ` fjahanian at apple dot com
2004-10-08 14:35 ` amacleod at redhat dot com
2004-10-08 16:24 ` fjahanian at apple dot com
2004-10-08 18:27 ` dalej at apple dot com
2004-10-08 18:37 ` amacleod at redhat dot com
2004-10-08 18:45   ` Diego Novillo
2004-10-08 18:45 ` dnovillo at redhat dot com
2004-10-08 18:48 ` fjahanian at apple dot com
2004-10-08 18:53 ` amacleod at redhat dot com
2004-10-08 19:25 ` fjahanian at apple dot com
2004-10-08 19:28 ` pinskia at gcc dot gnu dot org
2004-10-08 19:41 ` fjahanian at apple dot com
2004-10-08 21:04 ` dalej at apple dot com
2004-10-12 17:39 ` [Bug tree-optimization/17884] " rth at gcc dot gnu dot org
2004-10-12 18:30 ` dalej at apple dot com
2005-01-14 21:34 ` das at FreeBSD dot ORG
2005-01-20  1:33 ` rth at gcc dot gnu dot org
2005-02-02  7:18 ` rth at gcc dot gnu dot org
2005-10-01 19:48 ` pinskia at gcc dot gnu dot org

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=20041007193056.17884.fjahanian@apple.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).