From: Ian Lance Taylor <iant@google.com>
To: MikeW <mw_phil@yahoo.co.uk>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc optimises out test of value in register-only loop
Date: Fri, 14 Oct 2011 04:41:00 -0000 [thread overview]
Message-ID: <mcrobxk6v7l.fsf@coign.corp.google.com> (raw)
In-Reply-To: <loom.20111013T124012-691@post.gmane.org> (MikeW's message of "Thu, 13 Oct 2011 11:23:48 +0000 (UTC)")
MikeW <mw_phil@yahoo.co.uk> writes:
> volatile register int stop_loop __asm("r5")__;
gcc does not support volatile register variables. I think it could be
meaningful, but it has never worked.
Ian
next prev parent reply other threads:[~2011-10-14 4:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 11:35 MikeW
2011-10-13 11:38 ` Andrew Haley
2011-10-13 11:56 ` MikeW
2011-10-13 11:58 ` Thomas Martitz
2011-10-13 12:01 ` Andrew Haley
2011-10-13 12:14 ` MikeW
2011-10-13 12:18 ` Andrew Haley
2011-10-13 12:05 ` MikeW
2011-10-14 4:41 ` Ian Lance Taylor [this message]
2011-10-14 9:07 ` Andrew Haley
2011-10-15 3:20 ` Ian Lance Taylor
2011-10-17 8:30 ` Andrew Haley
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=mcrobxk6v7l.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mw_phil@yahoo.co.uk \
/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).