From owner-freebsd-toolchain@freebsd.org  Sun Feb  5 15:33:00 2017
Return-Path: <owner-freebsd-toolchain@freebsd.org>
Delivered-To: freebsd-toolchain@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31A46CD1C4D
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Sun,  5 Feb 2017 15:33:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1B81A1DB0
 for <freebsd-toolchain@FreeBSD.org>; Sun,  5 Feb 2017 15:33:00 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v15FWxFA034260
 for <freebsd-toolchain@FreeBSD.org>; Sun, 5 Feb 2017 15:32:59 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 216707] exp-run: Update lang/gcc from GCC 4.9 to GCC 5
Date: Sun, 05 Feb 2017 15:33:00 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: jbeich@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: portmgr@FreeBSD.org
X-Bugzilla-Flags: exp-run?
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-216707-29464-fonvR0Qtsi@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-216707-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-216707-29464@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-toolchain@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Maintenance of FreeBSD's integrated toolchain
 <freebsd-toolchain.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-toolchain/>
List-Post: <mailto:freebsd-toolchain@freebsd.org>
List-Help: <mailto:freebsd-toolchain-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain>, 
 <mailto:freebsd-toolchain-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 15:33:00 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216707

Jan Beich (mail not working) <jbeich@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jbeich@FreeBSD.org

--- Comment #17 from Jan Beich (mail not working) <jbeich@FreeBSD.org> ---
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.

(In reply to Gerald Pfeifer from comment #4)
> I guess it would be at least 50% or more above. (See the dependencies in
> PR 196712 for how much pain that last update was.)

Still peanuts compared to Clang/libc++ updates. ;)

--=20
You are receiving this mail because:
You are on the CC list for the bug.=