Schedule
April 25th, 2007 0:00AM -
April 27th, 2007 0:00AM (GMT / UTC)
SPOJ (CEST) is UTC +2, Beijing (CST) is UTC +8, and Hanoi is UTC +7
April 28th, 2007 0:00AM -
April 30th, 2007 0:00AM (GMT / UTC)
SPOJ (CEST) is UTC +2, Beijing (CST) is UTC +8, and Hanoi is UTC +7
Rules
Links
Amber's blog: http://adn.cn/blog/
Introductions to System
At present SPOJ uses the following status codes:
AC - accepted - your program ran successfully and gave a correct answer
WA - wrong answer - your program ran successfully, but gave an incorrect answer
TLE - time limit exceeded - your program was compiled successfully, but it didn't stop before the time limit
CE - compilation error - your program couldn't be compiled; compilation errors can be seen from www and are sent via mail if your preferences say so; note: only some languages can give CE, syntax errors in interpreted languages can lead to WA (Python - no pre-checking syntax or Perl - CE only afer a basic syntax check)
RE - runtime error - your program was compiled succesfully, but it exited with an error; possible codes are:
- SIGSEGV(signal 11) - most common, "segmentation fault";
- SIGXFSZ(signal 25) - "output limit exceeded";
- SIGFPE(signal 8) - "floating point error", like division by zero, etc...
- SIGABRT(signal 6) - raised by the program itself; C++ STL does it under some conditions;
- NZEC(non-zero exit code) - helps tell a crash from WA with interpreted languages;
- other - there are other signals which can cause the program to terminate, all remaining are shown as other.