Re: gcc optimises out test of value in register-only loop

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: MikeW <mw_phil@xxxxxxxxxxx>
Subject: Re: gcc optimises out test of value in register-only loop
From: Ian Lance Taylor <iant@xxxxxxxxxx>
Date: Thu, 13 Oct 2011 21:41:34 -0700
Cc: gcc-help@xxxxxxxxxxx
In-reply-to: <loom.20111013T124012-691@post.gmane.org> (MikeW's message of "Thu, 13 Oct 2011 11:23:48 +0000 (UTC)")
References: <loom.20111013T124012-691@post.gmane.org>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

MikeW <mw_phil@xxxxxxxxxxx> 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

Follow-Ups:
- Re: gcc optimises out test of value in register-only loop
  - From: Andrew Haley

References:
- gcc optimises out test of value in register-only loop
  - From: MikeW

Prev by Date: SIZE_TYPE
Next by Date: Re: SIZE_TYPE
Previous by thread: Re: gcc optimises out test of value in register-only loop
Next by thread: Re: gcc optimises out test of value in register-only loop
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux