Create a more organized (but still commented out as not very useful)

stub for OpenCL work. I can't really dig enough out of the commit log
messages other than to tell that a lot of work went into this in the 2.9
-> 3.0 timeframe. I'll let the folks touching it decide if it merits
a spot in the release notes and provide the appropriate details if so.

git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@145291 91177308-0d34-0410-b5e6-96231b3b80d8

1 files changed, 8 insertions, 2 deletions

diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index 321c86ac1f..0b203978a0 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -87,8 +87,6 @@ Clang's support for those languages.</p>
 the history. Anything still here needs to be distilled and turned into proper
 prose in a section of its own. When doing that, delete the notes.</p>
 <ul>
-  <li>OpenCL support -- need details from Tanya and Peter -- separate language
-  section?</li>
   <li>Building Clang on windows -- mingw, 32 and 64 bit, native windows builds,
   cygwin. get chapuni to flesh out details.</li>
   <li>Compiling C/C++ w/ MinGW (32/64) and Cygwin on Windows -- chapuni</li>
@@ -177,6 +175,14 @@ to introspect the preprocessing.
   <li>The exact source range for expanded macros can be retrieved.</li>
 </ul>
 
+<!--
+Need Peter and/or Tanya to flesh this out if we want it in 3.0's notes.. The
+state isn't clear just from documentation or commit logs.
+
+<h4 id="opencl">Initial work to support compiling OpenCL with Clang</h4>
+Clang has some (limited) support for compiling OpenCL.
+-->
+
 <!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->
 <h3 id="cchanges">C Language Changes in Clang</h3>
 <!-- = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = -->