Why not just build your release-build with gccgo? It often already gives better performance than gc, AIUI. If enough of the people who really care about it would focus their energy on it, that could probably get even more pronounced. There's no reason that gc needs to grow optimization knobs, if you can just use a different compiler.
On Sun, Jun 21, 2020 at 7:50 AM Tyler Compton <xavi...@gmail.com> wrote: > The idea of having development and release compilation modes sounds > appealing at first, though I'm a bit skeptical about how it would turn out. > This would mean that, during development, you wouldn't have a full > understanding of the performance characteristics of your program. > Admittedly, that's not something you *always* care about, but when you do > care you'll have to deal with slow compilation times. > > I've found that in C++ certain memory safety bugs will only rear their > ugly head after a certain compiler optimization level, meaning that these > bugs can be missed during development. Go's memory safety would probably > make this significantly less of a problem, but it still concerns me > somewhat. > > On Fri, Jun 19, 2020 at 6:46 PM David Skinner <skinner.da...@gmail.com> > wrote: > >> I remember going on a two-hour lunch break at a Cajun restaurant and >> returning to my office to discover that my precompiled C++ headers were >> still compiling. I really love that Go compiles quickly and links quickly. >> >> The day comes when code needs to ship, final compile, and final quality >> control tests, why not have a final build that compiles quite slowly and >> optimizes to the max. There is no need to do either/or and compromise, just >> do both. >> >> On Friday, June 19, 2020 at 12:23:46 PM UTC-5, Ronald Davilla wrote: >>> >>> Just if perfomance will decrease with every release/version, it'd be not >>> really good, and it's might be necessary to pay more attention to this >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "golang-nuts" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to golang-nuts+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/fd72210d-5a04-4be3-b51c-50b8313bf3dao%40googlegroups.com >> <https://groups.google.com/d/msgid/golang-nuts/fd72210d-5a04-4be3-b51c-50b8313bf3dao%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CAA%3DXfu1mBzN6YJJLtAOb1ZBPuDgXoCDzuG34x5XGPwTk1u-q8A%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nuts/CAA%3DXfu1mBzN6YJJLtAOb1ZBPuDgXoCDzuG34x5XGPwTk1u-q8A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAEkBMfEUp-x67iC6m3kH_0MQtG60WYArXg5QFEdcGOr5NgKi_g%40mail.gmail.com.
