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

Issue 5610048: [google] Backport ThreadSanitizer instrumentation pass from google/main to google/gcc-4_6 (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 2 months ago by dvyukov
Modified:
11 years, 7 months ago
CC:
gcc-patches_gcc.gnu.org
Base URL:
svn+ssh://gcc.gnu.org/svn/gcc/branches/google/gcc-4_6/
Visibility:
Public.

Patch Set 1 #

Patch Set 2 : [google] Backport ThreadSanitizer instrumentation pass from google/main to google/gcc-4_6 #

Patch Set 3 : address review comments #

Patch Set 4 : address review comments #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1486 lines, -3 lines) Patch
M gcc/ChangeLog.google-4_6 View 1 2 1 chunk +19 lines, -0 lines 0 comments Download
M gcc/Makefile.in View 1 2 3 chunks +8 lines, -1 line 0 comments Download
M gcc/common.opt View 1 2 1 chunk +8 lines, -0 lines 0 comments Download
M gcc/doc/invoke.texi View 1 2 4 chunks +14 lines, -2 lines 0 comments Download
M gcc/passes.c View 1 2 1 chunk +1 line, -0 lines 0 comments Download
A gcc/testsuite/gcc.dg/tsan.h View 1 2 1 chunk +102 lines, -0 lines 0 comments Download
A gcc/testsuite/gcc.dg/tsan-ignore.h View 1 2 1 chunk +5 lines, -0 lines 0 comments Download
A gcc/testsuite/gcc.dg/tsan-ignore.c View 1 2 1 chunk +53 lines, -0 lines 0 comments Download
A gcc/testsuite/gcc.dg/tsan-ignore.ignore View 1 2 1 chunk +7 lines, -0 lines 0 comments Download
A gcc/testsuite/gcc.dg/tsan-mop.c View 1 2 1 chunk +94 lines, -0 lines 0 comments Download
A gcc/testsuite/gcc.dg/tsan-stack.c View 1 2 1 chunk +34 lines, -0 lines 0 comments Download
M gcc/toplev.c View 1 2 2 chunks +5 lines, -0 lines 0 comments Download
M gcc/tree-pass.h View 1 2 1 chunk +1 line, -0 lines 0 comments Download
A gcc/tree-tsan.h View 1 2 1 chunk +26 lines, -0 lines 0 comments Download
A gcc/tree-tsan.c View 1 2 1 chunk +1109 lines, -0 lines 0 comments Download

Messages

Total messages: 6
dvyukov
This is for google/gcc-4_6 branch. Backport ThreadSanitizer (tsan) instrumentation pass from google/main. * tree-tsan.c: New ...
12 years, 2 months ago (2012-02-01 11:16:29 UTC) #1
Ollie Wild
Diego, can you look at this? Thanks, Ollie On Wed, Feb 1, 2012 at 5:16 ...
12 years, 2 months ago (2012-02-01 15:23:23 UTC) #2
Diego Novillo
On 2/1/12 3:16 AM, Dmitriy Vyukov wrote: > This is for google/gcc-4_6 branch. > Backport ...
12 years, 2 months ago (2012-02-01 18:05:15 UTC) #3
dvyukov
Index: gcc/doc/invoke.texi =================================================================== --- gcc/doc/invoke.texi (revision 183833) +++ gcc/doc/invoke.texi (working copy) @@ -306,6 +306,7 @@ ...
12 years, 2 months ago (2012-02-02 12:38:38 UTC) #4
dvyukov
On 2012/02/01 18:05:15, Diego Novillo wrote: > On 2/1/12 3:16 AM, Dmitriy Vyukov wrote: > ...
12 years, 2 months ago (2012-02-02 14:01:50 UTC) #5
Diego Novillo
12 years, 2 months ago (2012-02-02 16:44:48 UTC) #6
On Thu, Feb 2, 2012 at 06:01,  <dvyukov@google.com> wrote:

> Here I create a declaration for a var that is defined in our run-time
> library. If I use some real location, then the declaration will have
> different irrelevant locations in each TU (irrelevant, because it will
> be somewhere near begin of a first instrumented function), + there will
> be the definition with a correct location (inside of our run-time
> library). Does it make sense? The current situation (a lot of
> declarations with unknown location + definition with correct location)
> looks OK IMVHO.

Ah, OK.  In that case, that's fine.

> Does it make sense to set location for all tree's? I can't extract
> location from the sequence, because it's NULL (however, of course, I
> still can pass all the way down).

Just the statements.  I had missed the location setting you do at the
end.  That is fine.


Thanks.  Diego.
Sign in to reply to this message.

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