Re: I sent in a bug report and never heard anything back

2016-08-28 Thread Achim Gratz
jeff writes: > You are correct. The gcc people replied to my bug report with: > > "So the problem is your GMP/MPFR are compiled for one type of CPU and cannot > be > copied to other type." > > They closed it as a resolved issue. Correct, since it's not their bug. > So the problem is that gcc now

Re: I sent in a bug report and never heard anything back

2016-08-28 Thread Brian Inglis
On 2016-08-27 22:57, Brian Inglis wrote: On 2016-08-27 10:27, jeff wrote: Brian Inglis wrote: 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. My reply: You are correct. The gcc people repl

Re: I sent in a bug report and never heard anything back

2016-08-27 Thread Brian Inglis
On 2016-08-27 10:27, jeff wrote: Brian Inglis wrote: 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. My reply: You are correct. The gcc people replied to my bug report with: "So the problem

Re: I sent in a bug report and never heard anything back

2016-08-27 Thread jeff
Brian Inglis wrote: 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. My reply: You are correct. The gcc people replied to my bug report with: "So the problem is your GMP/MPFR are compiled

Re: I sent in a bug report and never heard anything back

2016-08-26 Thread jeff
Hans-Bernhard Bröker wrote: 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. My reply: While it is always possible that there is a hardware issue, I suspect that is not

Re: I sent in a bug report and never heard anything back

2016-08-26 Thread Brian Inglis
On 2016-08-26 11:55, Hans-Bernhard Bröker wrote: Am 26.08.2016 um 16:30 schrieb j...@jeffunit.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

Re: I sent in a bug report and never heard anything back

2016-08-26 Thread Hans-Bernhard Bröker
Am 26.08.2016 um 16:30 schrieb j...@jeffunit.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. it means the compiler has a bug (which I suspect is related

Re: I sent in a bug report and never heard anything back

2016-08-26 Thread Brian Inglis
On 2016-08-26 08:30, j...@jeffunit.com wrote: 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

Re: I sent in a bug report and never heard anything back

2016-08-26 Thread jeff
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 t

Re: I sent in a bug report and never heard anything back

2016-08-16 Thread Marco Atzeri
On 16/08/2016 18:07, j...@jeffunit.com wrote: I sent in http://sourceware.org/ml/cygwin/2016-08/msg0.html about an internal compiler error with gcc. It has been about 2 weeks and I have gotten no reply. It would be nice to fix this bug. thanks, jeff the code compile on both 32bit and 64

I sent in a bug report and never heard anything back

2016-08-16 Thread jeff
I sent in http://sourceware.org/ml/cygwin/2016-08/msg0.html about an internal compiler error with gcc. It has been about 2 weeks and I have gotten no reply. It would be nice to fix this bug. thanks, jeff -- Problem reports: http://cygwin.com/problems.html FAQ: http: