diff options
Diffstat (limited to 'community/gsoc/project_ideas/gcc_asan.mdwn')
| -rw-r--r-- | community/gsoc/project_ideas/gcc_asan.mdwn | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/community/gsoc/project_ideas/gcc_asan.mdwn b/community/gsoc/project_ideas/gcc_asan.mdwn index 229c46ec..21a30666 100644 --- a/community/gsoc/project_ideas/gcc_asan.mdwn +++ b/community/gsoc/project_ideas/gcc_asan.mdwn @@ -19,3 +19,28 @@ See also the [[valgrind]] task. A follow-up project is porting GCC's ThreadSanitizer. Possible mentors: Thomas Schwinge (tschwinge) + + +# IRC, OFTC, #gcc, 2012-12-11 + + <richi> hmm, is libtsan not multi-libbed? + <jakub> richi: it only works on x86_64 right now + <richi> ugh + <jakub> richi: so, it is multilibbed, but only built on multilibs and + targets which are supported + <jakub> richi: as it often needs lots of RAM, it is probably not going to + be supported on 32-bit targets at all + <jakub> richi: no reason not to support it on say ppc64 or sparc64 or s390x + I guess, just needs work + <richi> jakub: where is asan supported? everywhere? + <jakub> richi: but then, I haven't even read what exactly libtsan does, + only looked at the atomics in there, and did the GCC side from what I + knew should be instrumented + <jakub> richi: asan is right now supported on x86_64/i686, ppc/ppc64, + perhaps partially x86 darwin (don't care) and in theory arm (nobody + tested) + <jakub> richi: porting isn't that hard, but the library isn't as clean as + it would be desirable portability wise + <jakub> richi: that said, I don't want to spend as much time as I've done + so far on it, and in the time I'll allocate for it optimizing the code it + generates is higher on the todo list than ports to other targets |