[gsoc26] Add compiler-research and affiliated projects

_gsocorgs/2026/compres.md

@@ -0,0 +1,15 @@
+---
+title: "Compiler Research"
+author: "Aaron Jomy"
+layout: default
+organization: CompRes
+logo: CompRes-logo.png
+description: |
+  The Compiler Research Group is a group of programming language enthusiasts at Princeton University and CERN. It's primary goal is to foster innovation and excellence at the intersection of compiler research and data science. Our main focus areas include Interpretative C/C++/CUDA, Automatic Differentiation tools, and C++ Language Interoperability with Python. We aim to catalyze transformative advancements in scientific computing, fostering a community that thrives on shared knowledge and innovation.
+
+  Open projects beyond the following list can be found at https://compiler-research.org/open_projects
+  
+  In addition to reaching out to the mentors, prospective candidates are required to complete the following form: 
+---
+
+{% include gsoc_proposal.ext %}

_gsocprojects/2026/project_Clad.md

@@ -0,0 +1,16 @@
+---
+project: Clad
+layout: default
+logo: Clad-logo.png
+description: |
+  [Clad](https://clad.readthedocs.io/en/latest/) enables 
+  automatic differentiation (AD) for C++. It is based on LLVM compiler 
+  infrastructure and is a plugin for Clang compiler. Clad is based on 
+  source code transformation. Given C++ source code of a mathematical 
+  function, it can automatically generate C++ code for computing derivatives
+  of the function.
+summary: |
+  [Clad](https://clad.readthedocs.io/en/latest/) is an automatic differentiation (AD) tool for C++
+---
+
+{% include gsoc_project.ext %}

_gsocprojects/2026/project_CppInterOp.md

@@ -0,0 +1,11 @@
+---
+project: CppInterOp
+layout: default
+logo: InterOp-logo.png
+description: |
+  [CppInterOp](https://github.com/compiler-research/CppInterOp) is a C++ Interoperability library, which leverages ROOT's Cling and LLVM's Clang-REPL C++ interpreters, to provide a minimalist and backward-compatible API facilitating seamless language interoperability. This provides downstream interactive C++ tools with the compiler as a service by embedding Clang and LLVM as libraries in their codebases. By enabling dynamic Python interactions with static C++ codebases, CppInterOp enhances computational efficiency and rapid development in high-energy physics. The library offers primitives enabling cppyy, an automatic, run-time, Python-C++ bindings generator. The CppInterOp library provides a minimalist approach for other languages to bridge C++ entities (variables, classes, etc.). This enables interoperability with C++ code, bringing the speed and efficiency of C++ to simpler, more interactive languages like Python.
+summary: |
+  The [CppInterOp](https://github.com/compiler-research/CppInterOp) library provides a minimalist approach for other languages to bridge C++ entities (variables, classes, etc.). This enables interoperability with C++ code, bringing the speed and efficiency of C++ to simpler, more interactive languages like Python.
+---
+
+{% include gsoc_project.ext %}

_gsocprojects/2026/project_Xeus-Cpp.md

@@ -0,0 +1,18 @@
+---
+project: Xeus-Cpp
+layout: default
+logo: Xeus-Cpp-logo.png
+description: |
+  [Xeus-Cpp](https://xeus-cpp.readthedocs.io/en/latest/index.html) is a Jupyter kernel
+  for C++ based on the native implementation of the Jupyter protocol [xeus](https://github.com/jupyter-xeus/xeus).
+  It provides users with an interactive execution environment for C++ in Jupyter notebooks, built on LLVM's
+  [Clang-Repl](https://clang.llvm.org/docs/ClangRepl.html) C++ interpreter, provided by
+  the [CppInterOp](https://github.com/compiler-research/CppInterOp/) interoperability library. 
+  
+  This REPL (read-eval-print-loop) nature allows rapid prototyping and iterations without the overhead
+  of compiling and running separate C++ programs, allowing users to write and execute C++ code interactively.
+summary: |
+  [Xeus-Cpp](https://xeus-cpp.readthedocs.io/en/latest/index.html) is a Jupyter kernel for C++ based on the native implementation of the Jupyter protocol [xeus](https://github.com/jupyter-xeus/xeus).
+---
+
+{% include gsoc_project.ext %}

_gsocproposals/2026/proposal_CppInterop-API-ExposeMemory.md

@@ -0,0 +1,49 @@
+---
+title: Implement CppInterOp API exposing memory ownership and thread safety
+layout: gsoc_proposal
+project: CppInterOp
+year: 2025
+difficulty: medium
+duration: 350
+mentor_avail: June-October
+organization:
+  - CompRes
+project_mentors:
+  - email: [email protected]
+    organization: CERN/CompRes
+    first_name: Aaron
+    last_name: Jomy
+    is_preferred_contact: yes
+  - email: [email protected]
+    organization: CERN/Compres
+    first_name: Vipul
+    last_name: Cariappa
+  - email: [email protected]
+    organization: CompRes
+    first_name: Vassil
+    last_name: Vassilev
+---
+
+## Description
+
+Incremental compilation pipelines process code chunk-by-chunk by building an ever-growing translation unit. Code is then lowered into the LLVM IR and subsequently run by the LLVM JIT. Such a pipeline allows creation of efficient interpreters. The interpreter enables interactive exploration and makes the C++ language more user friendly. The incremental compilation mode is used by the interactive C++ interpreter, Cling, initially developed to enable interactive high-energy physics analysis in a C++ environment.
+
+Clang and LLVM provide access to C++ from other programming languages, but currently only exposes the declared public interfaces of such C++ code even when it has parsed implementation details directly. Both the high-level and the low-level program representation has enough information to capture and expose more of such details to improve language interoperability. Examples include details of memory management, ownership transfer, thread safety, externalized side-effects, etc. For example, if memory is allocated and returned, the caller needs to take ownership; if a function is pure, it can be elided; if a call provides access to a data member, it can be reduced to an address lookup. The goal of this project is to develop API for CppInterOp which are capable of extracting and exposing such information AST or from JIT-ed code and use it in cppyy (Python-C++ language bindings) as an exemplar. If time permits, extend the work to persistify this information across translation units and use it on code compiled with Clang.
+
+## Project Milestones
+
+* Collect and categorize possible exposed interop information kinds
+* Write one or more facilities to extract necessary implementation details
+* Design a language-independent interface to expose this information
+* Integrate the work in clang-repl and Cling
+* Implement and demonstrate its use in cppyy as an exemplar
+* Present the work at the relevant meetings and conferences.
+
+## Requirements
+
+* C++ programming
+* Python programming
+* Familiarity with Clang and LLVM IR
+
+## Links
+* [Repo](https://github.com/compiler-research/CppInterOp)