Re: [DNG] Gcc issue?

On Fri, Apr 22, 2016 at 01:53:11PM -0400, Steven W. Scott wrote: > Bogus mayhaps. Whatever the issue, it's been there a while because previous > versions fail as well. Having spent the first 25-30 years of my career in > assembly language, I completely understand "optimization" by a compiler; >

Re: [DNG] Gcc issue?

Bogus mayhaps. Whatever the issue, it's been there a while because previous versions fail as well. Having spent the first 25-30 years of my career in assembly language, I completely understand "optimization" by a compiler; it's a method used to attempt compensation for inherent inefficiencies in

Re: [DNG] Gcc issue?

On Fri, Apr 22, 2016 at 10:27:16AM +0200, parazyd wrote: > On Thu, 21 Apr 2016, Steven W. Scott wrote: > >Just curious, anyone else getting segfaults after compiling with gcc -O3 > >optimization flag on alpha 4? Same system, same code, same flags work ok > >on Wheezy. If I back down to

Re: [DNG] Gcc issue?

"Steven W. Scott" writes: > Just curious, anyone else getting segfaults after compiling with gcc -O3 > optimization flag on alpha 4? Same system, same code, same flags work ok on > Wheezy. If I back down to -O2 no problems. If the program segfaults reproducibly (or somewhat

Re: [DNG] Gcc issue?

Le 21/04/2016 20:38, KatolaZ a écrit : The simple reason is that the very same gcc has compiled at least 90% of the software you are using in alpha4, and who knows how many other millions of packages. So if there were any such bug in gcc, it would have probably been hit by now, just out of pure

Re: [DNG] Gcc issue?

On Thu, 21 Apr 2016, Steven W. Scott wrote: >Just curious, anyone else getting segfaults after compiling with gcc -O3 >optimization flag on alpha 4? Same system, same code, same flags work ok >on Wheezy. If I back down to -O2 no problems. > >I'm blaming gcc, but I was interested

Re: [DNG] Gcc issue?

Thanks all for the input . I'm definitely not ready to call it a bug, and always suspect my code first, but this is a new one on me and I'm stumped. You have given me new avenues to explore, and I am most appreciative. SWS On Thu, Apr 21, 2016 at 3:06 PM, Jaromil wrote: > On

Re: [DNG] Gcc issue?

On Thu, 21 Apr 2016, KatolaZ wrote: > Before going into finding gcc bugs, my humble suggestion is to give > a go to valgrind. It is a wise suggestion. All GNU C/C++ programmers should have several passes through valgrind on their code, this is should be perceived as a standard procedure.

Re: [DNG] Gcc issue?

On Thu, Apr 21, 2016 at 07:27:06PM +0100, KatolaZ wrote: > On Thu, Apr 21, 2016 at 02:15:52PM -0400, Steven W. Scott wrote: > > Just curious, anyone else getting segfaults after compiling with gcc -O3 > > optimization flag on alpha 4? Same system, same code, same flags work ok on > > Wheezy. If I

[DNG] Gcc issue?

Just curious, anyone else getting segfaults after compiling with gcc -O3 optimization flag on alpha 4? Same system, same code, same flags work ok on Wheezy. If I back down to -O2 no problems. I'm blaming gcc, but I was interested if anyone else had a similar experience or insight as to what might