octave-bug-tracker
[Top][All Lists]
Advanced

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

[Octave-bug-tracker] [bug #65321] C++20 warnings about deprecated uses o


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #65321] C++20 warnings about deprecated uses of volatile variables
Date: Fri, 16 Feb 2024 15:09:27 -0500 (EST)

URL:
  <https://savannah.gnu.org/bugs/?65321>

                 Summary: C++20 warnings about deprecated uses of volatile
variables
                   Group: GNU Octave
               Submitter: jwe
               Submitted: Fri 16 Feb 2024 08:09:27 PM UTC
                Category: Coding Style and Maintenance
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: jwe
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Any
           Fixed Release: None
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Fri 16 Feb 2024 08:09:27 PM UTC By: John W. Eaton <jwe>
I see the following warnings when compiling with GCC and using "-std=c++20":


87 occurrences: warning: '++' expression of 'volatile'-qualified type is
deprecated [-Wvolatile]
18 occurrences: warning: using value of assignment with 'volatile'-qualified
left operand is deprecated [-Wvolatile]
14 occurrences: warning: '--' expression of 'volatile'-qualified type is
deprecated [-Wvolatile]


It's probably worth examining why we thought it was necessary to use volatile
when declaring these variables.  If it was an attempt to ensure atomic
read/write behavior, then it would probably be better to use std::atomic.  For
other things, maybe there is also a better way now than using volatile? 
Either way, we should try to avoid the warnings.








    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65321>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

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