# | User | Rating |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 151 |
Name |
---|
You were using Clang++17 Diagnostics, as name suggest it meant to diagnose error in runtime. Since it runs sanitizers it will consume more memory, and will be significantly slower (I think up to 10x).
You can read more about it here: https://codeforces.net/blog/entry/55902?locale=en.
You should never use it as primary compiler, even if you are locally using clang, everything will be fine with g++ as long as you are writing correct c++ code, and you are locally using same c++ standard (--std=c++14/17).
If there are disparities between two compilers its either clang/gcc bug(very unlikely), undefined behavior, or incorrect code.
You can read this wonderful blog https://codeforces.net/blog/entry/15547 that will help you catch some silly mistakes.
Also duplicate of https://codeforces.net/blog/entry/92795.
Next time please add Codeforces submissions ID (ML: 128563183, OK 128563258), because it kinda not polite to ask for help, and expect people to go look into your submissions history
what's the problem?
brew install gcc