[SERVER-17864] boost::optional triggers spurious -Wmaybe-uninitialized warnings on g++ Created: 02/Apr/15  Updated: 19/Sep/15  Resolved: 09/Apr/15

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: 3.1.2

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Mathias Stearn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-17635 Improve SortedDataInterface::Cursor API Closed
Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 3.1.1, Quint Iteration 3.1.2
Participants:

 Description   

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47679
http://stackoverflow.com/questions/21755206/how-to-get-around-gcc-void-b-4-may-be-used-uninitialized-in-this-funct

Reported to boost as https://svn.boost.org/trac/boost/ticket/11169.



 Comments   
Comment by Githook User [ 09/Apr/15 ]

Author:

{u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}

Message: SERVER-17864 Work around -Wmaybe-uninitialized warnings with boost::optional on g++
Branch: master
https://github.com/mongodb/mongo/commit/8b31673665dd2a9d38e4b65ea880fc49acc0bd81

Generated at Thu Feb 08 03:45:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.