Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(6)

Issue 4959053: Thread safety: No thread safety analysis option

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 7 months ago by supertri
Modified:
12 years, 7 months ago
Reviewers:
chandlerc
Visibility:
Public.

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+14 lines, -0 lines) Patch
M lib/Sema/AnalysisBasedWarnings.cpp View 1 chunk +4 lines, -0 lines 2 comments Download
M test/SemaCXX/warn-thread-safety-analysis.cpp View 2 chunks +10 lines, -0 lines 0 comments Download

Messages

Total messages: 2
chandlerc
http://codereview.appspot.com/4959053/diff/1/lib/Sema/AnalysisBasedWarnings.cpp File lib/Sema/AnalysisBasedWarnings.cpp (right): http://codereview.appspot.com/4959053/diff/1/lib/Sema/AnalysisBasedWarnings.cpp#newcode1333 lib/Sema/AnalysisBasedWarnings.cpp:1333: // FIXME: follow the decl chain for enclosing contexts ...
12 years, 7 months ago (2011-09-02 06:45:58 UTC) #1
supertri
12 years, 7 months ago (2011-09-02 22:25:09 UTC) #2
http://codereview.appspot.com/4959053/diff/1/lib/Sema/AnalysisBasedWarnings.cpp
File lib/Sema/AnalysisBasedWarnings.cpp (right):

http://codereview.appspot.com/4959053/diff/1/lib/Sema/AnalysisBasedWarnings.c...
lib/Sema/AnalysisBasedWarnings.cpp:1333: // FIXME: follow the decl chain for
enclosing contexts to identify any
On 2011/09/02 06:45:58, chandlerc wrote:
> What decl chain? We don't support nested functions.
> 
> Are you imagining constructs such as this?
> 
> void f() __attribute__((no_thread_safety_analysis));
> void f() {
>   struct S {
>     void m() {
>       // do something unsafe
>     }
>   };
>   // ...
> }
> 
> If so, I would gladly not support that. Force the programmer to annotate each
> function explicitly.
> 

Ok, sounds good. FIXME removed.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b