2026 ICPC World Finals Dubai Programming Environment

This page describes current plans for the Programming Environment which will be available to each WF team.   Please note that these plans are subject to change.   See the "Update History" list at the bottom of this page for information on the currency of what is shown here.   Also, see the section on Build Instructions, below, for information on how to install the WF Programming Environment on your own machine.

Hardware:

Each team at the ICPC World Finals contest will be provided with one workstation.  The configuration of the workstation will be as follows:

• System Unit:
  • TBD
• Screen: Minimum 21" full-HD (1920x1080); details to be posted soon...
• Keyboard: wired English keyboard with Standard US layout; details to be determined (a keyboard image will be posted here).
• External mouse: wired 3-button mouse; details to be determined (a mouse image will be posted here).

No hardware substitutions will be allowed (that is, teams may not bring their own equipment onto the contest floor).  This includes that teams may not substitute keyboards or other peripherals; all teams will use identical equipment, as described above, during the contest.

Software:

The software configuration will consist of the following:

• OS:
  • Ubuntu 24.04.1 LTS Linux (64-bit) with Linux kernel 6.8.0-45-generic. A list of packages included in the OS image can be found here.
• Desktop:
  • GNOME
• Editors
  • vi/vim
  • gvim
  • emacs
  • gedit
  • geany
  • kate
• Languages:
  • Java
    • Openjdk version 21.0.4
      • 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 version 13.2.0 with compiler flags: -x c -g -O2 -std=gnu11 -static {files} -lm
  • C++
    • g++ version 13.2.0 with compiler flags: -x c++ -g -O2 -std=gnu++20 -static {files}
  • Python 3
    • PyPy3 version 7.3.15 with GCC 13.2.0 providing Python 3.9.18
      • A list of the installed Python modules can be found here.
    • Note that Python 2 is not supported at the ICPC World Finals.
  • 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

• IDEs:
  • Eclipse 4.33.0 (2024-09), configured with:
    • JDT (Java Development Tools) version 3.19.600.v20240903-0240 using Java as listed above)
    • CDT (C/C++ Development Tools) version 11.6.1 202407022008 using C/C++ as listed above)
    • PyDev (Python Development Environment) version 13.0.0.202502031104 using Python 3 as listed above)
  • IntelliJ (IDEA Community Edition version 2024.2.3), configured with:
    • Java as listed above
    • Kotlin as listed above
  • CLion (version 2024.2.2), configured with:
    • C/C++ as listed above
  • Pycharm Community Edition Python IDE (version 2024.2.3), configured with:
    • Python 3 as listed above
  • Code::Blocks (version 20.03+svn13046-0.3build2), configured with:
    • C/C++ as listed above
  • Visual Studio Code (version 1.93.1), configured with:
    • Microsoft C/C++ . (Note that the Judges will compile C/C++ programs with GCC as listed above, not with Microsoft C/C++.)

Compilation of Submissions

During the contest, teams will submit proposed solutions to the contest problems to the Judges using the PC-Squared Contest Control System. Check the PC² Team Guide for further details.

Source files submitted to the Judges will be compiled using the language systems and flags described above.

The "{files}" in the above descriptions represents the list of source files from the submission which will actually be compiled. Files with the following suffixes (and only files with these suffixes) will be submitted to the compiler:

• For C submissions: files ending with .c
• For C++ submissions: files ending with .cc, .cpp, .cxx, or .c++
• For Java submissions: files ending with .java
• For Python submissions: files ending with .py
• For Kotlin submissions: files ending with .kt

Execution of Submissions

For each language, if the compilation step is successful then the submission will be executed as follows:

• For C/C++:  the executable file generated by the compiler will be executed to generate the output of the submission.  

• For Python 3: the main source file will be executed by the PyPy3 Python3 interpreter to generate the output of the submission.

• For Java: the compiled main class will be executed using the java command with the runtime flags listed above.

• For Kotlin: the compiled main class will be executed using the kotlin command with the runtime flags listed above.

Compilation and execution as described above will take place in a "sandbox" on a dedicated judging machine.  The judging machine will be as identical as possible to, and at least as powerful as, the machines used by teams.  The sandbox will allocate memory according to the memory limit specified in the problem statement; the entire program, including its runtime environment, must execute within this memory limit.  For interpreted languages (Java, Python, and Kotlin) the runtime environment includes the interpreter (that is, the JVM for Java/Kotlin and the Python interpreter for Python).

The sandbox memory allocation size will be the same for all languages.

Build Instructions:

Instructions for building a system identical to what is planned for team use at the WF are posted here.  Please note that the image created by these instructions is a draft, subject to changes as we approach the contest.  See the Revised  date at the bottom of that page to determine the most recent change date.

Reference Materials:

These packages will be available on team machines at the World Finals, and will be installed automatically as part of the steps listed under Build Instructions, above. 

• JDK JavaDocs
• C++ STL docs 
• PC Team Guide (as linked above)
• Additional Information:
  • Judging Notes (TBD)
  • Technical Notes (TBD)

We welcome all suggestions and comments.  This configuration is subject to change until the final update.  All questions about the system configuration should be directed to John Clevenger, WF Technical Director.

Update History

---