OpenIndiana Hipster 2020.04 Released: Phase Out Python 2, GCC7 as Base Compiler

Re:OpenIndiana Hipster 2020.04 Released: Phase Out Python 2,... by rbanffy on Tuesday May 05, 2020 @08:09PM (#23086566)

I'm now curious about how are you abusing your compilers. I've never seen GCC crash because of the code I've written.

[ Parent | on HN ]

Re:OpenIndiana Hipster 2020.04 Released: Phase Out Python 2,... by RcouF1uZ4gsC on Tuesday May 05, 2020 @08:41PM (#23086761)

Try C++ template meta programming. I lost count of the number of times I have crashed Clang and GCC.

[ Parent | on HN ]

Re:OpenIndiana Hipster 2020.04 Released: Phase Out Python 2,... by ndesaulniers on Tuesday May 05, 2020 @10:52PM (#23087502)

Once you start throwing tens of millions of lines at them, crashes become quite more frequent.

[ Parent | on HN ]

Re:OpenIndiana Hipster 2020.04 Released: Phase Out Python 2,... by rurban on Thursday May 07, 2020 @02:22AM (#23100265)

Using the latest features. Like -O4 -flto=4 cef retpoline and such. But mostly it's the simple things, like the string library, which broke in 9. Only 50% of the added bugs fixed so far. They are moving too fast.

[ Parent | on HN ]

Re:OpenIndiana Hipster 2020.04 Released: Phase Out Python 2,... by throwaway_pdp09 on Wednesday May 06, 2020 @03:55AM (#23088795)

To all the people who will now let us know that GCC crashes for them (and I've no doubt it does, I'm not questioning your honesty), do you put in bug reports?

[ Parent | on HN ]

Re:OpenIndiana Hipster 2020.04 Released: Phase Out Python 2,... by rurban on Thursday May 07, 2020 @02:19AM (#23100242)

If they care yes. For gcc it's an unpleasant experience. And minimizing the testcases is an art lost to me.

For llvm it's pleasent.

[ Parent | on HN ]