From f814a37622cc76188990ef0d86cdf0d4e51ac5e1 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Mon, 10 Oct 2011 12:49:14 +0200 Subject: open_issues/code_analysis: Two more items on GCC warnings. --- open_issues/code_analysis.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) 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, + , 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]] -- cgit v1.2.3