public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: gcc-bugzilla@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: [Bug tree-optimization/24146] Optimizes away FPU control word store
Date: Fri, 30 Sep 2005 14:07:00 -0000 [thread overview]
Message-ID: <1128089169.9435.45.camel@IBM-82ZWS052TEN> (raw)
In-Reply-To: <20050930135810.2808.qmail@sourceware.org>
On Fri, 2005-09-30 at 13:58 +0000, rearnsha at gcc dot gnu dot org
wrote:
> ------- Additional Comments From rearnsha at gcc dot gnu dot org 2005-09-30 13:58 -------
> (In reply to comment #1)
> > volatile is needed here.
>
> No, the manual says:
> An @code{asm} instruction without any output operands will be treated
> identically to a volatile @code{asm} instruction.
>
> So this insn should be kept even though it isn't explicitly volatile.
>
Then i guess we should teach the FE to just mark them volatile, so we
don't have to worry about this in the middle end.
next prev parent reply other threads:[~2005-09-30 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 13:42 [Bug tree-optimization/24146] New: " rguenth at gcc dot gnu dot org
2005-09-30 13:46 ` [Bug tree-optimization/24146] " pinskia at gcc dot gnu dot org
2005-09-30 13:58 ` rearnsha at gcc dot gnu dot org
2005-09-30 14:07 ` Daniel Berlin [this message]
2005-09-30 14:00 ` [Bug tree-optimization/24146] [4.0 Regression] " rguenth at gcc dot gnu dot org
2005-09-30 14:04 ` pinskia at gcc dot gnu dot org
2005-09-30 14:07 ` pinskia at gcc dot gnu dot org
2005-09-30 14:18 ` Daniel Berlin
2005-09-30 14:07 ` dberlin at dberlin dot org
2005-09-30 14:11 ` bonzini at gcc dot gnu dot org
2005-09-30 14:11 ` bonzini at gcc dot gnu dot org
2005-09-30 14:17 ` pinskia at gcc dot gnu dot org
2005-09-30 14:19 ` dberlin at dberlin dot org
2005-09-30 14:36 ` [Bug middle-end/24146] [4.0/4.1 Regression] ASMs with no output are not marked as volatile pinskia at gcc dot gnu dot org
2005-09-30 19:52 ` rth 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=1128089169.9435.45.camel@IBM-82ZWS052TEN \
--to=dberlin@dberlin.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-bugzilla@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).