ICPC EUC 2026 – Programming Environment

This document describes the planned programming environment that will be available to each team at the ICPC Europe Championship (EUC) 2026.
Please note that these plans are subject to change. See the Update History section at the end of this document for information on the currency of these specifications.

1. Hardware

Each team will be assigned one workstation during the contest. The workstation will have the following configuration:

System Unit

  • Laptop: Dell Latitude 5495
  • CPU: AMD R5 2500U
  • Memory: 16 GB

External Devices

  • Monitor: Lenovo ThinkVision T23i-10, 23″, resolution 1920×1080
  • Keyboard: Logitech K120 (US-International layout)
  • Mouse: Logitech B100

Image of the keyboard and mouse are provided below.

No hardware substitutions are permitted.
Teams may not bring or use their own laptops, keyboards, mice, or any other peripherals. All contestants must use the equipment provided.

2. Software

The software configuration for EUC 2026 is as follows:

Operating System

  • Debian 13 (GNU/Linux x86_64)

Desktop Environment

  • Xfce 4.20

Text Editors (terminal-based)

  • vi / vim
  • nano
  • mcedit
  • joe
  • neovim

Graphical Text Editors

  • Sublime Text
  • gedit
  • thonny
  • gvim
  • mousepad
  • emacs
  • kate
  • scite

3. Programming Languages and Compilers

Java (OpenJDK 21.0.9)

  • Compiler flags:
    -encoding UTF-8 -sourcepath . -d . {files}
  • Runtime flags:
    -Dfile.encoding=UTF-8 -XX:+UseSerialGC -Xss64m -Xms{memlim}m -Xmx{memlim}m

C (gcc 14.2.0)

  • Compiler flags:
    -O3 -std=gnu17 -static {files} -lm

C++ (g++ 14.2.0)

  • Compiler flags:
    -O3 -std=c++23 -static {files}

Python 3 (PyPy 7.3.19 and Python 3.13)

A list of installed Python modules is provided here.

Kotlin (version 1.9.24)

  • Compiler flags:
    -d . {files}
  • Runtime flags:
    -Dfile.encoding=UTF-8 -J-XX:+UseSerialGC -J-Xss64m -J-Xms{memlim}m -J-Xmx{memlim}m

4. Integrated Development Environments (IDEs)

IntelliJ IDEA (Community Edition, 2024.2)

Configured for:

  • Java
  • Kotlin

CLion (2024.2)

Configured for:

  • C / C++

PyCharm (Community Edition, 2024.2)

Configured for:

  • Python 3

Code::Blocks (version 25.03, 2025-03-29)

Configured for:

  • C / C++

VS Codium (version 1.75.0)

Extensions included:

  • Microsoft C/C++ extension v1.13.9
  • Microsoft Python extension v2023.4.1

Note:
Judges will compile and execute C/C++ submissions using the compilers listed under Languages, not the Microsoft C/C++ toolchain.

5. Debuggers and Profilers

The following tools will be available:

  • gdb
  • lldb
  • ddd
  • valgrind
  • gprof

6. Compilation of Submissions

Teams will submit solutions through the SIO2 Contest Control System, which will be open for testing in January 2026.

Submissions will be compiled using the language systems and flags listed in this document.

The placeholder {files} refers to all submitted source files with valid suffixes:

  • C: .c
  • C++: .cpp
  • Java: .java
  • Python: .py
  • Kotlin: .kt

Only files with the above suffixes will be compiled.

7. Execution of Submissions

If compilation succeeds, the programs will be executed as follows:

C / C++

The generated executable will be run directly.

Python 3

The main source file will be executed using the PyPy3 interpreter.

Java

The compiled main class will be executed using java with the runtime flags listed above.

Kotlin

The compiled main class will be executed using kotlin with the runtime flags listed above.

Execution will take place in a sandbox on a dedicated judging machine.
This machine will be as close as possible to — and at least as powerful as — the contestant machines.

Memory in the sandbox will match the problem-specific memory limit, and the entire program including the runtime environment must operate within this limit.

For interpreted languages (Java, Python, Kotlin), the interpreter (JVM or Python runtime) counts toward the memory limit.

The sandbox memory allocation will be the same across all languages.

8. Reference Materials Available on Team Machines

  • JDK JavaDocs
  • C++ STL documentation
  • Python 3.13 documentation
  • gcc, gdb, and valgrind documentation

9. Feedback and Changes

Suggestions and comments regarding this configuration are welcome.
All elements of this environment remain subject to change until the final update.

Update History

  • 02 December 2025: Initial version