avr-libc-commit
[Top][All Lists]
Advanced

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

[avr-libc-commit] [2541] Submitted by Britton Kerin:


From: j
Subject: [avr-libc-commit] [2541] Submitted by Britton Kerin:
Date: Sun, 11 Jun 2017 11:41:47 -0400 (EDT)

Revision: 2541
          http://svn.sv.gnu.org/viewvc/?view=rev&root=avr-libc&revision=2541
Author:   joerg_wunsch
Date:     2017-06-11 11:41:47 -0400 (Sun, 11 Jun 2017)
Log Message:
-----------
Submitted by Britton Kerin:
patch #8650: another small doc fix in atomic.h
* include/util/atomic.h: Improve documentation.

Ticket Links:
------------
    http://savannah.gnu.org/patch/?8650

Modified Paths:
--------------
    trunk/avr-libc/ChangeLog
    trunk/avr-libc/include/util/atomic.h

Modified: trunk/avr-libc/ChangeLog
===================================================================
--- trunk/avr-libc/ChangeLog    2017-06-11 15:35:05 UTC (rev 2540)
+++ trunk/avr-libc/ChangeLog    2017-06-11 15:41:47 UTC (rev 2541)
@@ -1,6 +1,12 @@
 2017-06-11  Joerg Wunsch <address@hidden>
 
        Submitted by Britton Kerin:
+       patch #8650: another small doc fix in atomic.h
+       * include/util/atomic.h: Improve documentation.
+
+2017-06-11  Joerg Wunsch <address@hidden>
+
+       Submitted by Britton Kerin:
        patch #8649: small documentation fixes in
        * include/util/atomic.h: Improve documentation.
 

Modified: trunk/avr-libc/include/util/atomic.h
===================================================================
--- trunk/avr-libc/include/util/atomic.h        2017-06-11 15:35:05 UTC (rev 
2540)
+++ trunk/avr-libc/include/util/atomic.h        2017-06-11 15:41:47 UTC (rev 
2541)
@@ -94,8 +94,8 @@
     Interrupt Status (I) bit of the SREG register. Exit paths from
     both block types are all managed automatically without the need
     for special considerations, i. e. the interrupt status will be
-    restored to the same value it has been when entering the
-    respective block.
+    restored to the same value it had when entering the respective
+    block (unless ATOMIC_FORCEON or NONATOMIC_FORCEOFF are used).
 
     A typical example that requires atomic access is a 16 (or more)
     bit variable that is shared between the main execution path and an




reply via email to

[Prev in Thread] Current Thread [Next in Thread]