Keyboard Shortcuts

File
u :up to issue
m :publish + mail comments
M :edit review message
j / k :jump to file after / before current file
J / K :jump to next file with a comment after / before current file
Side-by-side diff
i :toggle intra-line diffs
e :expand all comments
c :collapse all comments
s :toggle showing all comments
n / p :next / previous diff chunk or comment
N / P :next / previous comment
<Up> / <Down> :next / previous line
<Enter> :respond to / edit current comment
d :mark current comment as done
Issue
u :up to list of issues
m :publish + mail comments
j / k :jump to patch after / before current patch
o / <Enter> :open current patch in side-by-side view
i :open current patch in unified diff view
Issue List
j / k :jump to issue after / before current issue
o / <Enter> :open current issue
# : close issue
Comment/message editing
<Ctrl> + s or <Ctrl> + Enter :save comment
<Esc> :cancel edit
Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(50)
Issues Repositories Search
Open Issues | Closed Issues | All Issues | Sign in with your Google Account to create issues and add comments

Issue 4964080: Refactoring error messages

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

Patch Set 1 #

Total comments: 10
Created: 14 years, 4 months ago
Download [raw] [tar.bz2]
Unified diffs Side-by-side diffs Delta from patch set Stats (+77 lines, -127 lines) Patch
M include/clang/Analysis/Analyses/ThreadSafety.h View 2 chunks +21 lines, -17 lines 8 comments Download
M include/clang/Basic/DiagnosticSemaKinds.td View 1 chunk +1 line, -1 line 2 comments Download
M lib/Analysis/ThreadSafety.cpp View 5 chunks +21 lines, -80 lines 0 comments Download
M lib/Sema/AnalysisBasedWarnings.cpp View 1 chunk +15 lines, -12 lines 0 comments Download
M test/SemaCXX/warn-thread-safety-analysis.cpp View 5 chunks +19 lines, -17 lines 0 comments Download
Total messages: 2
|
chandlerc
LGTM w/ the comments below... http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/ThreadSafety.h File include/clang/Analysis/Analyses/ThreadSafety.h (right): http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/ThreadSafety.h#newcode63 include/clang/Analysis/Analyses/ThreadSafety.h:63: /// \enum SK_LockedSomePredecessors -- ...
14 years, 3 months ago (2011年09月15日 00:40:53 UTC) #1
LGTM w/ the comments below...
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
File include/clang/Analysis/Analyses/ThreadSafety.h (right):
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:63: /// \enum
SK_LockedSomePredecessors -- a mutex is locked in some but not all
I wonder if there is a less technical description here... LockedSomePaths?
Also, rather than "Some" maybe we want a better word. We want a word that more
clearly is strictly greater than zero, and strictly less than all... Not coming
up with anything better than "some" though...
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:66: /// function.
Same enum comment comment as the other patch...
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:99: /// 2, or a mutex is only
held at the start of some loop iterations,
Typically formal lists place the conjunction on the prior item:
1. Foo is true, or
2. Bar is true, or
3. Baz is true.
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:104: /// \param LEK -- which of
the three above cases we should warn for
ErrorKind?
http://codereview.appspot.com/4964080/diff/1/include/clang/Basic/DiagnosticSe...
File include/clang/Basic/DiagnosticSemaKinds.td (left):
http://codereview.appspot.com/4964080/diff/1/include/clang/Basic/DiagnosticSe...
include/clang/Basic/DiagnosticSemaKinds.td:1398: "mutex '%0' is still held at
the end of function '%1'">,
I'm sad to see this bit of information leave the diagnostic... can we get it
back?
Sign in to reply to this message.
supertri
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/ThreadSafety.h File include/clang/Analysis/Analyses/ThreadSafety.h (right): http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/ThreadSafety.h#newcode63 include/clang/Analysis/Analyses/ThreadSafety.h:63: /// \enum SK_LockedSomePredecessors -- a mutex is locked in ...
14 years, 3 months ago (2011年09月15日 17:21:28 UTC) #2
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
File include/clang/Analysis/Analyses/ThreadSafety.h (right):
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:63: /// \enum
SK_LockedSomePredecessors -- a mutex is locked in some but not all
On 2011年09月15日 00:40:53, chandlerc wrote:
> I wonder if there is a less technical description here... LockedSomePaths?
> 
> Also, rather than "Some" maybe we want a better word. We want a word that more
> clearly is strictly greater than zero, and strictly less than all... Not
coming
> up with anything better than "some" though...
Also could not come up with anything better (and neither could the person
sitting next to me on the bus). Changed to LockedSomePaths.
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:66: /// function.
On 2011年09月15日 00:40:53, chandlerc wrote:
> Same enum comment comment as the other patch...
Done.
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:99: /// 2, or a mutex is only
held at the start of some loop iterations,
On 2011年09月15日 00:40:53, chandlerc wrote:
> Typically formal lists place the conjunction on the prior item:
> 
> 1. Foo is true, or
> 2. Bar is true, or
> 3. Baz is true.
Yes, yes they do.
http://codereview.appspot.com/4964080/diff/1/include/clang/Analysis/Analyses/...
include/clang/Analysis/Analyses/ThreadSafety.h:104: /// \param LEK -- which of
the three above cases we should warn for
On 2011年09月15日 00:40:53, chandlerc wrote:
> ErrorKind?
Done.
http://codereview.appspot.com/4964080/diff/1/include/clang/Basic/DiagnosticSe...
File include/clang/Basic/DiagnosticSemaKinds.td (left):
http://codereview.appspot.com/4964080/diff/1/include/clang/Basic/DiagnosticSe...
include/clang/Basic/DiagnosticSemaKinds.td:1398: "mutex '%0' is still held at
the end of function '%1'">,
On 2011年09月15日 00:40:53, chandlerc wrote:
> I'm sad to see this bit of information leave the diagnostic... can we get it
> back?
Added a FIXME for now. It may be easier to put back after subsequent refactoring
changes. Once DeLesley has finished implementing code to deal with all gcc test
cases, you guys should think carefully about the error message text.
Sign in to reply to this message.
|
Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b

AltStyle によって変換されたページ (->オリジナル) /