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:message-id:date:subject:from:to:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=bQx
	1NjJdsSY3w+ifavdboQ7qQliRPLAcw7qKV6Ze8ppb1wjQRqYq3KaCRbNLswMOgUJ
	NBjpriZCtU/d2xcFEAA2Yz0e/69OlJE+vqROb/p+b1b9fnrQ7HfB4dTnaplVFguq
	pjjPYxFUZzT/vJXPi8PbQqGMpVZbN5uTLsSPgtDE=
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:message-id:date:subject:from:to:mime-version
	:content-type:content-transfer-encoding; s=default; bh=W5vKbIHt0
	3fWtJ52E7N2B+4d4A8=; b=DH32jiITgI6OnNTCP7T8Vp6Sl7/FTmmcvkyZVNZMp
	Txgj3RWSqEA0t7fISS8bFHXrppLYz55vwXhkJAm57oCCsdh6byYWS6rrAxyiL6Jd
	Yh2C83y0w+/+CWbLjyq2ZxgVoeChXPj05I8m4iJ9rRaFNNhx66NEajSAQUpACu9+
	VM=
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=1.2 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=dell, Input, notebook, H*u:SquirrelMail
X-HELO:	homiemail-a59.g.dreamhost.com
Message-ID:	<1d53db9147e25c0c5b7e2ba863fd021a.squirrel@webmail.weasel.com>
Date:	Fri, 26 Aug 2016 07:30:21 -0700
Subject:	Re: I sent in a bug report and never heard anything back
From:	jeff AT jeffunit DOT com
To:	cygwin AT cygwin DOT com
User-Agent:	SquirrelMail/1.4.21
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u7QEUvE5013800

In reference to http://sourceware.org/ml/cygwin/2016-08/msg00261.html

I wrote:
I have a small program that generates an internal compiler error.
This only happens on a new dell notebook with an Intel 3825U pentium .
The code compiles and runs fine on an older xeon and amd processors.
Enclosed is the output of cygcheck.

Here is what happens when I try to compile:

sh-4.3$ gcc bug_f2.c
bug_f2.c: In function 'Round':
bug_f2.c:23:5: internal compiler error: Illegal instruction
     return floor(d + 0.5);
     ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
sh-4.3$ exit

Here is the source code:

/#include <string.h>             /* strlen */
#include <math.h>               /* floor */
#include <limits.h>             /* INT_MAX, INT_MIN */
#include <assert.h>             /* assert */


/*+Input:       A double.
   Output:      Rounded input.
   Action:      Rounded input. +*/
extern double Round(double d)
{
    return floor(d + 0.5);
}



Marco Atzeri wrote:

the code compile on both 32bit and 64 bit version of gcc
for me.

As it is a not stand alone program

  gcc -c  bug_f2.c

should be used.

My reply:

Thanks for noting the code compiles on 32 and 64 bit architectures.
The code is over a decade old, and has compiled and worked on many ersions
of cygwin
and linux. I specifically mentioned it compiled on cygwin with different
processors.
That was never in question.

The issue is the internal compiler error coming from gcc on my dell with a
specific
intel processor. An internal compiler error does not mean the source code
has a syntax error,
it means the compiler has a bug (which I suspect is related to the
specific cpu).

Based on myexperience, the two most likely possibilities are:
1) somehow my cygwin installation is bad. That is why I included the
output of cygcheck.
2) there is a cpu specific internal compiler error with gcc.

If 1) is the case, it is possible there is a bug with the cygwin
installer. If 2) is the case,
then the bug should be reported to the gcc maintainers. Since the compiler
is a bit old,
I suspect they will say update the compiler, which is likely something
that cygwin should
do ao it may benefit everyone, not just me.

thanks,
jeff




--
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

- Raw text -