From 3eecfde70f519820c49495297ca9e19c280477b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alex=20Clark=20=E2=98=BA?= Date: Fri, 14 Feb 2014 01:59:10 -0800 Subject: [PATCH] Updated GSOC Ideas (markdown) --- GSOC-Ideas.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/GSOC-Ideas.md b/GSOC-Ideas.md index 2e2db85..ca6a711 100644 --- a/GSOC-Ideas.md +++ b/GSOC-Ideas.md @@ -1,6 +1,4 @@ -Welcome to the Pillow wiki for GSOC Ideas! - -If selected, we plan to focus on improving the following: +Welcome to the Pillow wiki for GSOC Ideas! If selected, we plan to focus on the following: ## Documentation @@ -10,8 +8,12 @@ _From Prashant Shrivastava, a potential GSOC participant who contacted Alex Clar ## Performance +_Suggested by Eric Soroos, Mentor + Investigate speeding up core operations by vectorizing core functionality. This could be a combination of autovectorization in the compiler, manual recoding of tight loops in vector form, or writing kernels for OpenCL. ## Stability +_Suggested by Eric Soroos, Mentor + Pillow decodes a lot of image formats, some of which are safer and better specified than others. Experience with [other projects](http://googleonlinesecurity.blogspot.com/2014/01/ffmpeg-and-thousand-fixes.html) has shown that there are many bugs lurking in otherwise functional code. Running a large corpus of valid, invalid, or otherwise fuzzed images while recording and investigating errors and crashes should improve the robustness of Pillow. \ No newline at end of file