From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) by sourceware.org (Postfix) with ESMTPS id 80FA23857022 for ; Thu, 13 May 2021 01:41:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 80FA23857022 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([68.147.0.90]) by shaw.ca with ESMTP id h0Llli8LniLmnh0Lmlk5ZG; Wed, 12 May 2021 19:41:18 -0600 X-Authority-Analysis: v=2.4 cv=W+Nb6Tak c=1 sm=1 tr=0 ts=609c83be a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] Test: {mingw64-{i686,x86_64}-,}gcc-11.1.0-0.1 To: cygwin@cygwin.com References: <0c2f908b-d3ac-5bd6-92b1-c2bd0970ec24@gmail.com> <7abf399d-1844-16da-ce49-afe442509ad3@towo.net> From: Brian Inglis Organization: Systematic Software Message-ID: <20f80861-efa7-5f65-8d70-94fa7793812d@SystematicSw.ab.ca> Date: Wed, 12 May 2021 19:41:17 -0600 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: <7abf399d-1844-16da-ce49-afe442509ad3@towo.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-CA Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4xfFN7UXTyg9A9FT/B+lEoQUKpSK+wPdUjI/fRPcZlLYSlX52CHo/8TkGjqLg8QdjBJOCAfSq0UxzyuLu61cgBSQC08Mrkd4vhx9VhEwr2215gVKJFYbR0 vbOiHIiiL11o82vYCeaFGVw65EdZAwigFiCOVyzJ+KY3C7+jnnqZYj4SApzq6YqR7N3MQ5+g7qGI4u3LhJ/3EHe1xM7dXROVjFA= X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2021 01:41:22 -0000 On 2021-05-12 12:30, Thomas Wolff wrote: > 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. Do you mean that building mintty with gcc 11 -O2 breaks mintty? >>>>   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... -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]