summaryrefslogtreecommitdiff
path: root/community
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-01-08 21:34:29 +0100
committerThomas Schwinge <thomas@codesourcery.com>2013-01-08 21:43:11 +0100
commitcd42b6144bf707fa38555bc06e267bb16db011f5 (patch)
treeddebd4ae1c845bd062261b4335a9ab7a969a3c89 /community
parenta91114fc89dd554494801349e57bd5d29454a8b1 (diff)
parente66cb01b99b60f9483de2425bca3bb104bcc9ae8 (diff)
Merge remote-tracking branch 'fp/master'
Diffstat (limited to 'community')
-rw-r--r--community/gsoc/project_ideas/gcc_asan.mdwn25
-rw-r--r--community/gsoc/project_ideas/smp.mdwn7
2 files changed, 31 insertions, 1 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
diff --git a/community/gsoc/project_ideas/smp.mdwn b/community/gsoc/project_ideas/smp.mdwn
index e17c2ccf..d9788e56 100644
--- a/community/gsoc/project_ideas/smp.mdwn
+++ b/community/gsoc/project_ideas/smp.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -14,3 +14,8 @@ License|/fdl]]."]]"""]]
# IRC, freenode, #hurd, 2012-09-30
<braunr> i expect smp to be our next gsoc project
+
+
+## IRC, freenode, #hurd, 2013-01-02
+
+ <braunr> i'd like to mentor someone for adding smp to gnumach