https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216707
--- Comment #18 from Pedro F. Giffuni <p...@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. Having > more > results at once would speed up fixing similar issues en masse using portmgr > hatchet^W blanket, a win in the long run. If there're many misoptimizations > or > compiler crashes we can backtrack to GCC 6 or just temporarily pin those few > 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. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-toolchain@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"
