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:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=FucaOt8Ccl2LpV9u 27Qm6RAIN0c9+P3rgea2tNq5PJI8NK067DMTbCJI4MJt7V6YMtKTkfjRMt+VFyUp i0JJoEnRqtqtzHfMGAgnL647DifXZfcVwxemZdGp9mtSBGIfLJdw+sCG9pY3X19z GP0Qkpdi173S1/a2aTm0ANwXJU4= 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:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=Y0gU7lR14E/kL/gukClL/+ DVoAE=; b=A+lFZe6DpLyxcFjdlRB/sU7360XFlLldVvlsng5QvTEUoohYAdYYKI TgGYM+87sEfYBrao2Mh2nHVf/pPqgCj6mmNivQ1dFBuqr9OtRjHAOVprkrgBaMkE C4ZlIyBai2rhU0oo2ZJHnx8hcAoknzlBASPWsaFPKrbYId4+D4Ub4= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=1.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=ram, specifics, faulty, H*f:sk:c423565 X-HELO: smtp-out-no.shaw.ca X-Authority-Analysis: v=2.2 cv=eo2d9chX c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=kkLwFqq4AAAA:8 a=X7obEGpRt7SpIH7RyiQA:9 a=QEXdDO2ut3YA:10 a=o8OmvK1q9j2rsWQQ_NmD:22 Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: I sent in a bug report and never heard anything back References: <1d53db9147e25c0c5b7e2ba863fd021a DOT squirrel AT webmail DOT weasel DOT com> To: cygwin AT cygwin DOT com From: Brian Inglis Message-ID: Date: Fri, 26 Aug 2016 13:37:55 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-CMAE-Envelope: MS4wfOT9NL6TxI9zraFTyfJOykRRaPPQN6fjpUGm1e/1/eqTHharV7kIxNzuMgb5HbYKjejejSDpcizWkekcUNjY1CSsweNkyLSIp1lltGpsJ4E1EK5bRchu fv0kOQObsN5smPaPNy99i9owSeE53/zv1q3KQW83mMEOZ97GgV+QaSc78aH9xsIbFuQUba9RR3KGbA== X-IsSubscribed: yes On 2016-08-26 11:55, Hans-Bernhard Bröker wrote: > Am 26.08.2016 um 16:30 schrieb jeff AT jeffunit DOT com: > >> The issue is the internal compiler error coming from gcc on my dell >> with a specific intel processor. > > I don't remember you telling one the specifics of that specific > processor, yet. Apparently it's a mobile Broadwell without AVX or AVX2, which might be assumed present in gcc as compiled, requiring a custom gcc build to run on that cpu. >> it means the compiler has a bug (which I suspect is related to the >> specific cpu). > > Not necessarily. Traditionally the typical reason for GCC internal > compiler errors, particularly if they occur with old source on very > new machines, has been faulty hardware. Most common reason appears to be lack of available memory, requiring 2GB to run comfortably. Allocating a few GB of paging space (recommend 2x ram) to Windows can allow heavy crunchers with large data requirements to run more comfortably. -- 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