Date: Sun, 05 Feb 2017 16:07:04 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216707] exp-run: Update lang/gcc from GCC 4.9 to GCC 5 Message-ID: <bug-216707-13-kjRgjEh71K@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-216707-13@https.bugs.freebsd.org/bugzilla/> References: <bug-216707-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216707 --- Comment #18 from Pedro F. Giffuni <pfg@FreeBSD.org> --- (In reply to Jan Beich (mail not working) from comment #17) > Hmm, not much bustage thanks to DragonFly dogfooding GCC 5 before us. :). > (In reply to Pedro F. Giffuni from comment #3) >> why not jump directly to GCC6 instead of GCC5? > > Why not GCC 7? exp-runs are slow and often contain false positives. Havin= g more > results at once would speed up fixing similar issues en masse using portm= gr=20 > hatchet^W blanket, a win in the long run. If there're many misoptimizatio= ns or=20 > compiler crashes we can backtrack to GCC 6 or just temporarily pin those = few=20 > ports to an older version. GCC version bumps are not fun so yes, it would be nicer to be a step ahead. IMO, the criteria is that GCC 6 is the latest supported version. GCC 7 is likely to be unstable enough upstream won't do any claims. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216707-13-kjRgjEh71K>