visus
/
toolchain-gcc-arm-embedded
Tarkkaile 1
Äänestä 0
Fork 0
Koodi Ongelmat 0 Pull-pyynnöt 0 Julkaisut 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commitit
1 Haara
Puu: 898a39b5ab
Branchit Tagit
${ item.name }
Create branch ${ searchTerm }
from '898a39b5ab'
${ noResults }
toolchain-gcc-arm-embedded/share/doc/gcc-arm-none-eabi/html/gcc/C_002b_002b-Volatiles.html

140 lines
6.4KB
Raaka Blame Historia 

  1. <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

  2. <html>

  3. <!-- Copyright (C) 1988-2020 Free Software Foundation, Inc.

  4. 

  5. Permission is granted to copy, distribute and/or modify this document

  6. under the terms of the GNU Free Documentation License, Version 1.3 or

  7. any later version published by the Free Software Foundation; with the

  8. Invariant Sections being "Funding Free Software", the Front-Cover

  9. Texts being (a) (see below), and with the Back-Cover Texts being (b)

  10. (see below).  A copy of the license is included in the section entitled

  11. "GNU Free Documentation License".

  12. 

  13. (a) The FSF's Front-Cover Text is:

  14. 

  15. A GNU Manual

  16. 

  17. (b) The FSF's Back-Cover Text is:

  18. 

  19. You have freedom to copy and modify this GNU Manual, like GNU

  20.      software.  Copies published by the Free Software Foundation raise

  21.      funds for GNU development. -->

  22. <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ -->

  23. <head>

  24. <meta http-equiv="Content-Type" content="text/html; charset=utf-8">

  25. <title>C++ Volatiles (Using the GNU Compiler Collection (GCC))</title>

  26. 

  27. <meta name="description" content="C++ Volatiles (Using the GNU Compiler Collection (GCC))">

  28. <meta name="keywords" content="C++ Volatiles (Using the GNU Compiler Collection (GCC))">

  29. <meta name="resource-type" content="document">

  30. <meta name="distribution" content="global">

  31. <meta name="Generator" content="makeinfo">

  32. <link href="index.html#Top" rel="start" title="Top">

  33. <link href="Option-Index.html#Option-Index" rel="index" title="Option Index">

  34. <link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">

  35. <link href="C_002b_002b-Extensions.html#C_002b_002b-Extensions" rel="up" title="C++ Extensions">

  36. <link href="Restricted-Pointers.html#Restricted-Pointers" rel="next" title="Restricted Pointers">

  37. <link href="C_002b_002b-Extensions.html#C_002b_002b-Extensions" rel="prev" title="C++ Extensions">

  38. <style type="text/css">

  39. <!--

  40. a.summary-letter {text-decoration: none}

  41. blockquote.indentedblock {margin-right: 0em}

  42. blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}

  43. blockquote.smallquotation {font-size: smaller}

  44. div.display {margin-left: 3.2em}

  45. div.example {margin-left: 3.2em}

  46. div.lisp {margin-left: 3.2em}

  47. div.smalldisplay {margin-left: 3.2em}

  48. div.smallexample {margin-left: 3.2em}

  49. div.smalllisp {margin-left: 3.2em}

  50. kbd {font-style: oblique}

  51. pre.display {font-family: inherit}

  52. pre.format {font-family: inherit}

  53. pre.menu-comment {font-family: serif}

  54. pre.menu-preformatted {font-family: serif}

  55. pre.smalldisplay {font-family: inherit; font-size: smaller}

  56. pre.smallexample {font-size: smaller}

  57. pre.smallformat {font-family: inherit; font-size: smaller}

  58. pre.smalllisp {font-size: smaller}

  59. span.nolinebreak {white-space: nowrap}

  60. span.roman {font-family: initial; font-weight: normal}

  61. span.sansserif {font-family: sans-serif; font-weight: normal}

  62. ul.no-bullet {list-style: none}

  63. -->

  64. </style>

  65. 

  66. 

  67. </head>

  68. 

  69. <body lang="en">

  70. <a name="C_002b_002b-Volatiles"></a>

  71. <div class="header">

  72. <p>

  73. Next: <a href="Restricted-Pointers.html#Restricted-Pointers" accesskey="n" rel="next">Restricted Pointers</a>, Up: <a href="C_002b_002b-Extensions.html#C_002b_002b-Extensions" accesskey="u" rel="up">C++ Extensions</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Option-Index.html#Option-Index" title="Index" rel="index">Index</a>]</p>

  74. </div>

  75. <hr>

  76. <a name="When-is-a-Volatile-C_002b_002b-Object-Accessed_003f"></a>

  77. <h3 class="section">7.1 When is a Volatile C++ Object Accessed?</h3>

  78. <a name="index-accessing-volatiles-1"></a>

  79. <a name="index-volatile-read-1"></a>

  80. <a name="index-volatile-write-1"></a>

  81. <a name="index-volatile-access-1"></a>

  82. 

  83. <p>The C++ standard differs from the C standard in its treatment of

  84. volatile objects.  It fails to specify what constitutes a volatile

  85. access, except to say that C++ should behave in a similar manner to C

  86. with respect to volatiles, where possible.  However, the different

  87. lvalueness of expressions between C and C++ complicate the behavior.

  88. G++ behaves the same as GCC for volatile access, See <a href="C-Extensions.html#C-Extensions">Volatiles</a>, for a description of GCC&rsquo;s behavior.

  89. </p>

  90. <p>The C and C++ language specifications differ when an object is

  91. accessed in a void context:

  92. </p>

  93. <div class="smallexample">

  94. <pre class="smallexample">volatile int *src = <var>somevalue</var>;

  95. *src;

  96. </pre></div>

  97. 

  98. <p>The C++ standard specifies that such expressions do not undergo lvalue

  99. to rvalue conversion, and that the type of the dereferenced object may

  100. be incomplete.  The C++ standard does not specify explicitly that it

  101. is lvalue to rvalue conversion that is responsible for causing an

  102. access.  There is reason to believe that it is, because otherwise

  103. certain simple expressions become undefined.  However, because it

  104. would surprise most programmers, G++ treats dereferencing a pointer to

  105. volatile object of complete type as GCC would do for an equivalent

  106. type in C.  When the object has incomplete type, G++ issues a

  107. warning; if you wish to force an error, you must force a conversion to

  108. rvalue with, for instance, a static cast.

  109. </p>

  110. <p>When using a reference to volatile, G++ does not treat equivalent

  111. expressions as accesses to volatiles, but instead issues a warning that

  112. no volatile is accessed.  The rationale for this is that otherwise it

  113. becomes difficult to determine where volatile access occur, and not

  114. possible to ignore the return value from functions returning volatile

  115. references.  Again, if you wish to force a read, cast the reference to

  116. an rvalue.

  117. </p>

  118. <p>G++ implements the same behavior as GCC does when assigning to a

  119. volatile object&mdash;there is no reread of the assigned-to object, the

  120. assigned rvalue is reused.  Note that in C++ assignment expressions

  121. are lvalues, and if used as an lvalue, the volatile object is

  122. referred to.  For instance, <var>vref</var> refers to <var>vobj</var>, as

  123. expected, in the following example:

  124. </p>

  125. <div class="smallexample">

  126. <pre class="smallexample">volatile int vobj;

  127. volatile int &amp;vref = vobj = <var>something</var>;

  128. </pre></div>

  129. 

  130. <hr>

  131. <div class="header">

  132. <p>

  133. Next: <a href="Restricted-Pointers.html#Restricted-Pointers" accesskey="n" rel="next">Restricted Pointers</a>, Up: <a href="C_002b_002b-Extensions.html#C_002b_002b-Extensions" accesskey="u" rel="up">C++ Extensions</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Option-Index.html#Option-Index" title="Index" rel="index">Index</a>]</p>

  134. </div>

  135. 

  136. 

  137. 

  138. </body>

  139. </html>