From owner-freebsd-toolchain@freebsd.org  Thu Aug 18 20:01:54 2016
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 238B8BBE7B8
 for <freebsd-toolchain@mailman.ysv.freebsd.org>;
 Thu, 18 Aug 2016 20:01:54 +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 1230C18F0
 for <freebsd-toolchain@FreeBSD.org>; Thu, 18 Aug 2016 20:01:54 +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 u7IK1rJ2065568
 for <freebsd-toolchain@FreeBSD.org>; Thu, 18 Aug 2016 20:01:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-toolchain@FreeBSD.org
Subject: [Bug 211864] LLVM is using AVX instructions for CPUTYPE=btver1 (AMD
 Bobcat)
Date: Thu, 18 Aug 2016 20:01:53 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 11.0-RC1
X-Bugzilla-Keywords: needs-qa, patch, regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: dim@FreeBSD.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: dim@FreeBSD.org
X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211864-29464-ls3Xi3Ovbr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211864-29464@https.bugs.freebsd.org/bugzilla/>
References: <bug-211864-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.22
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: Thu, 18 Aug 2016 20:01:54 -0000

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

--- Comment #7 from Dimitry Andric <dim@FreeBSD.org> ---
(In reply to Michel Depeige from comment #6)
> Will this fix be in RC2 ?

I will merge it to stable/11 on August 20, when the timeout expires.  Then I
will contact the Release Engineering team for permission to merge it to the
11.0 release branch.

This is not really a showstopper though, since you can work around it
relatively easily by setting your CPUTYPE to something else.  It is up to t=
he
Release Engineering team to decide.

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