[wwwdocs] PATCH for Re: going from SunOS 5/SparcWorks -> Linux/gcc

2011-04-26 Thread Gerald Pfeifer
Hi Paweł, On Thu, 29 Apr 2010, Paweł Sikora wrote: >> The standard 1st questions are: >> 1) Did you compile with -Wall -Wextra and solve all warnings? >> 2) Did you try with -fno-strict-aliasing? > for legacy code, the '-fwrapv' could be helpful. your mail reminded me that we could/should clarify

Re: going from SunOS 5/SparcWorks -> Linux/gcc

2010-04-29 Thread Paweł Sikora
On Thursday 29 April 2010 20:35:23 Steven Bosscher wrote: > The standard 1st questions are: > 1) Did you compile with -Wall -Wextra and solve all warnings? > 2) Did you try with -fno-strict-aliasing? for legacy code, the '-fwrapv' could be helpful.

Re: going from SunOS 5/SparcWorks -> Linux/gcc

2010-04-29 Thread Steven Bosscher
On Thu, Apr 29, 2010 at 8:25 PM, Brian Hill wrote: > I have an 15-year old C program (which I didn't write) that compiles and > runs fine with SparcWorks cc on Sun SPARC with SunOS 5.10. > > It compiles on CentOS 5 64-bit with gcc 4.1.2 but core dumps all over the > place. > > Switching to 32-bit

going from SunOS 5/SparcWorks -> Linux/gcc

2010-04-29 Thread Brian Hill
I have an 15-year old C program (which I didn't write) that compiles and runs fine with SparcWorks cc on Sun SPARC with SunOS 5.10. It compiles on CentOS 5 64-bit with gcc 4.1.2 but core dumps all over the place. Switching to 32-bit compile doesn't help much. I did as much debugging as I cou