X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 60A0D3853824
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=towo.net
Authentication-Results:	sourceware.org; spf=none smtp.mailfrom=towo AT towo DOT net
Subject:	Re: [ANNOUNCEMENT] Test: {mingw64-{i686,x86_64}-,}gcc-11.1.0-0.1
To:	cygwin AT cygwin DOT com
References:	<announce DOT 871raewgfm DOT fsf AT Rainer DOT invalid>
	<f3f9f296-cde2-1549-e7e9-38c1c855d5df AT towo DOT net>
	<0c2f908b-d3ac-5bd6-92b1-c2bd0970ec24 AT gmail DOT com>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<7abf399d-1844-16da-ce49-afe442509ad3@towo.net>
Date:	Wed, 12 May 2021 20:30:21 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
	Thunderbird/78.10.1
MIME-Version:	1.0
In-Reply-To:	<0c2f908b-d3ac-5bd6-92b1-c2bd0970ec24@gmail.com>
X-Provags-ID:	V03:K1:rH8mjvEfjuM3i3HNsNCSF9NNFsnCyZUIP7Vdehk516HjS6tU8wR
	/vBYl3Z6A1WDkE0rW7FKhILKord08eXZmrRqrHTe4HrMilLl68Z8EGEQUUYC/KZ+fzY/s+M
	Gr177BoHSy2+ikvf2nZGGqsnX/zvghfii1KnBHy7bdC4WaPJdn2ooF9JmjO96/la4EVHbro
	VCFeqSEUaXXZSRVIf+xEw==
X-UI-Out-Filterresults:	notjunk:1;V03:K0:QCxlyOf8lXk=:/FIWnbJNLLwCdi82S7oTQL
	fz6/SJYTBN2OxokrhyarYyvZi2ZpULRkxqvc+4SeEnBWsGZYssXyykfHyxIIDzCvBDtILGb7t
	LwdJQxRk2j4odPmko4kZBSvZG2/KVMJmaMXZkBTXIcCyCUOa7MgJ3ogZsRvRsjB5z/x9fR/qG
	XslCC1VJ31JpQoHaF60Yx9mWbK5W8EUeSdlHc1XWvn68KC7PKO3mSz/z8LQmX5NQYWjzIO5wi
	HoWkqjav29jcq8ZYaUGQ9GpXtuX8gCS1hqchMaegURJy9HEh4bi1mG0xULYj14bGZXs8inLmX
	YN4vCWc6TQqEukEihzHjaeyXxwkajYS8U80YgHai45FLwOua+pWFpesuVv0k6OPHoAUnr5CDw
	il812larlN20DEvIrAqzzqrqqZgR5b91eWk8k7jLqfTOcLw3pzbOEGsoaL3T1buBCsrIGLab+
	4TmPzuNAv8zKC/s7dJTztaOMbMPkeQgOV3afAxXJpLo48vyQ688AOMNb0bgyickfmfjYSSDrt
	JObJa6O2S6zZDyUI4K8w+Q=
X-Spam-Status:	No, score=-1.4 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 14CIUTeK021306

Am 12.05.2021 um 12:42 schrieb Jonathan Yong via Cygwin:
> On 5/12/21 9:14 AM, Thomas Wolff wrote:
>> Am 10.05.2021 um 21:13 schrieb Achim Gratz:
>>> The native and mingw-w64 cross compilers have been updated for both
>>> architectures to the latest upstream release version:
>>>
>>>   gcc-11.1.0-0.1
>> Are there any known problems with gcc 11? My program crashes if 
>> compiled with gcc -O2; gcc -O1 works, gcc 10 also works.
>> Thomas
>>
>>>   mingw64-i686-gcc-11.1.0-0.1
>>>   mingw64-x86_64-gcc-11.1.0-0.1
>>>
>>> This test release includes libgccjit as a separate package for the
>>> native toolchain on both architectures.  Since Cygwin can't use ASLR 
>>> any
>>> nontrivial dynamic objects that get created in this way will likely 
>>> need
>>> to get rebased before they can be used (especially on 32bit). It is
>>> unlikely that build systems recognize the need for doing that at the
>>> moment.
>>>
>>> Please test these compilers with your packages and applications as
>>> extensively as possible (especially if you are a Cygwin package
>>> maintainer).  Unless problems are found that necessitate another round
>>> of testing, the plan is to bootstrap the support libraries with the new
>>> toolchain and do a non-test update in about two to four weeks.
>>>
>>
>>
>
> Does stripping the optimized executable fix things?
No
> Are you also able to produce a minimal test case? 
Hardly. Behaviour is totally erratic. If I let the stacktrace tell me 
where it crashed and make the function empty, it happens somewhere else...

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

- Raw text -