X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=CuG52xc07GQQGFcA
	ycj8UVG2NZMmXK3fSSYCuAqRuPE0Kf9is1wELpKmXuUKQQux/ds5t7P9RFTuk05o
	L00oMorrYvqV7N7mqNHRNm4OKWppUpjrtRTzXEgfnW3cfv9zvgMiHieFqAMX4m9Q
	DFetvak3gFfid3wQYpvKjjMfL2k=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=dHa1ZAq8/KzzfI3/xdI9Iw
	G+qyE=; b=No0PsJu4ZmO1qaMCSY09G5I8ZlnKqbAkMFgtO64U6Bdt87S6QRBW53
	gcBc5lB9uc5JxlUdbSdczYYq9N0LoHw7on12VIE6qhrATlm0e5UHTOj7jHeqinrU
	LFoB4VDL5MEBc+QiKM8+2gVqs1GmEmEGB71MTjeI7Pll+hkP6vFh4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=calgary, H*RU:!192.168.1.100!, H*r:ip*192.168.1.100, Hx-spam-relays-external:!192.168.1.100!
X-HELO: smtp-out-so.shaw.ca
X-Authority-Analysis: v=2.2 cv=NKylwwyg c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=N659UExz7-8A:10 a=w5aJ8kaLLAry8Qfnm_kA:9 a=pILNOxqGKmIA:10
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Upstream Spectre CVE Patch Availability
To: cygwin AT cygwin DOT com
References: <d68cd57a-2de5-ddcb-0654-473d1713e260 AT SystematicSw DOT ab DOT ca>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <b0809df2-94b7-381f-1ead-bffdccd5ad25@SystematicSw.ab.ca>
Date: Thu, 18 Jan 2018 18:55:27 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <d68cd57a-2de5-ddcb-0654-473d1713e260@SystematicSw.ab.ca>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfEO0HKIHBlW2EGcZa59kQr+Ciu0KJzaQHpQwzx03MIJXMfDNaeNpKHJX63QwOkkOnyWbRlgPdePkt2JJ7bSns7k0x81wkZ86XeaiIgjiVJ7YDRKKComc vr6jddnzwF/69caypQQ/RZr/2jxqJ4cYsxDVubySs0HGwCbDsyCvvdbg/TvdX5S4sPvYSEz8iUJMJw==
X-IsSubscribed: yes

On 2018-01-18 18:45, Brian Inglis wrote:
> Hi folks,
> 
> Not seen any posts here about the monster in the chip yet (although those who
> might know may be busy dealing with the issues in their jobs), so has anyone any
> idea if or when we might see upstream Spectre CVE patches available for the
> following packages, whose bases have been mentioned in the many articles
> published recently, and has anyone seen mention of any other packages likely to
> be affected?
> 
> cygwin32-gcc-core 6.4.0-1
> djgpp-gcc-core 5.4.0-1
> gcc-core 6.4.0-4
> libjavascriptcoregtk3.0_0 2.0.4-5
> libvirt-common 3.6.0-1
> libwebkitgtk3.0_0 2.0.4-5
> mingw64-i686-gcc-core 6.4.0-1
> mingw64-x86_64-gcc-core 6.4.0-2

Forgot about:

llvm 5.0.1-1

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple