26 engineers on Hacker News describe using GCC first-hand: 4 endorse it, 3 regret it, 0 are mixed.
“GCC has built-in dimensional analysis, which has saved me from errors that would have otherwise taken hours to track down”
endorse · personal · LiamPowell · 2024-12-04 · source ↗ · wrong label?“with gcc or clang that works regardless of platform, with compiler-specific options.”
endorse · personal · adrian_b · 2023-12-26 · source ↗ · wrong label?“we were really feeling the pain of this. The compiler we were shackled to was many years out of date.”
regret · production · allenbrunson · 2018-01-15 · source ↗ · wrong label?“we switched to the NXP LPC platform using only open source tools: GCC ARM Embedded toolchain, OpenOCD + gdb for debugging and vim, make as 'IDE'. What a relief.”
endorse · production · ijager · 2014-04-27 · source ↗ · wrong label?“Also gcc is extremely demanding in terms of memory.”
regret · production · shin_lao · 2011-12-19 · source ↗ · wrong label?“So I've been using this GCC install on my Mac: Couple hundred megabytes.”
endorse · personal · trimbo · 2011-10-30 · source ↗ · wrong label?“We use a lot of C++ templates and gcc compilation times are a big pain point.”
regret · production · dirtyaura · 2010-10-07 · source ↗ · wrong label?“I now have a test to make sure my XOF code generates correct vectors with both GCC and clang”
neutral · production · strenholme · 2026-09-22 · source ↗ · wrong label?“gcc/clang exits. compilation is complete.”
neutral · personal · CuriousCosmic · 2022-11-22 · source ↗ · wrong label?“A while ago at my company we switched from GCC to Clang, and noticed a couple of massive regressions”
neutral · production · sakras · 2022-11-14 · source ↗ · wrong label?“things work fine in msvc/GCC/clang”
neutral · production · jcelerier · 2022-10-30 · source ↗ · wrong label?“We've found numerous bugs in gcc, clang and postgres by building / testing with unreleased compilers.”
neutral · production · anarazel · 2020-06-04 · source ↗ · wrong label?“Javac was used by hand, as was nasm/ld/gcc.”
neutral · personal · shean_massey · 2020-04-12 · source ↗ · wrong label?“at least in the 4.2/4.4 GCC versions, pre-caching the end() iterator of an STL collection before the loop”
neutral · production · berkut · 2018-12-31 · source ↗ · wrong label?“This works really well in practice for us. We use GCC to compile.”
neutral · production · gnulinux · 2018-12-28 · source ↗ · wrong label?“they are fully integrated with GCC and autotools and so on”
neutral · production · rwmj · 2018-11-26 · source ↗ · wrong label?“I just compiled it with the latest GCC and glibc, and carried on with my day”
neutral · personal · groovy2shoes · 2016-12-28 · source ↗ · wrong label?“goal #1 is just clean compiles w/ no warnings as errors”
neutral · production · hermitdev · 2016-12-06 · source ↗ · wrong label?“which disappeared when we switched to GCC.”
neutral · production · tobias3 · 2015-12-21 · source ↗ · wrong label?“pip[3], rust[4], mongo, consul[4], openldap[1], gcc[3] and several other things fail your criteria”
neutral · production · deathanatos · 2015-03-31 · source ↗ · wrong label?“ASAN isn't an option at my university because we use an older version of g++”
neutral · personal · turck3 · 2014-12-08 · source ↗ · wrong label?“Some of our code used GCC nested functions, which Clang did not support.”
neutral · production · inglorion · 2014-02-25 · source ↗ · wrong label?“we obviously didn't enable PGO/LTO for GCC either when doing these tests as that would have been pointless.”
neutral · personal · gillianseed · 2011-12-19 · source ↗ · wrong label?“we get significantly better performance with this than under Unix with GCC.”
neutral · production · TwoBit · 2011-12-19 · source ↗ · wrong label?“I've been using g++-4.6 lately and with the new lambdas I'm migrating more and more to this async task application model.”
neutral · personal · marshray · 2011-11-21 · source ↗ · wrong label?