summaryrefslogtreecommitdiff
path: root/open_issues
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2011-10-10 12:49:14 +0200
committerThomas Schwinge <thomas@schwinge.name>2011-10-10 15:15:45 +0200
commitf814a37622cc76188990ef0d86cdf0d4e51ac5e1 (patch)
treed6a987dd76ae3330fb7d3a1b1ab0aa26eb2fcfeb /open_issues
parentbb575aa59db86a51e09016bb12e5fae47d051e38 (diff)
open_issues/code_analysis: Two more items on GCC warnings.
Diffstat (limited to 'open_issues')
-rw-r--r--open_issues/code_analysis.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/open_issues/code_analysis.mdwn b/open_issues/code_analysis.mdwn
index 6cb304ef..e8e5ba0e 100644
--- a/open_issues/code_analysis.mdwn
+++ b/open_issues/code_analysis.mdwn
@@ -28,6 +28,14 @@ There is a [[!FF_project 276]][[!tag bounty]] on some of these tasks.
* [[GCC]]'s warnings. Yes, really.
+ * GCC plugins can be used for additional semantic analysis. For example,
+ <http://lwn.net/Articles/457543/>, and search for *kernel context* in
+ the comments.
+
+ * Have GCC make use of [[RPC]]/[[microkernel/mach/MIG]] *in*/*out*
+ specifiers, and have it emit useful warnings in case these are pointing
+ to uninitialized data (for *in* only).
+
* [Static Source Code Analysis Tools for C](http://spinroot.com/static/)
* [[!wikipedia List_of_tools_for_static_code_analysis]]