Date: Sat, 7 May 2005 00:05:16 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 550 ************************************************** Friday 06 May 2005 Number 550 ************************************************** Subjects for today 1 Re: Innotek GCC & Python : Paul Smedley" **= Email 1 ==========================** Date: Fri, 06 May 2005 12:57:13 +0930 From: "Paul Smedley" Subject: Re: Innotek GCC & Python Hi Andy, On 4/5/2005, "Andrew MacIntyre" wrote: >Paul Smedley wrote: >I quote from configure.in: > "# Python violates C99 rules, by casting between incompatible > # pointer types. GCC may generate bad code as a result of that, > # so use -fno-strict-aliasing if supported." > >Whether this will change anything I don't know, but I have seen a couple >of reports of it mattering on Linux. Sometimes I've found it worthwhile >to drop the optimisation level from -O3 to -Os to see whether behaviour >changes. Adding that switch certainly cleaned up the log files but didn't change anything else, neither did reducing the optimisation level. I'm tending towards calling convention being the root cause.... I had to modify the .DEF file for _curses_module & _curses_panel to add an _ but maybe it's trying to call _curses.dll without the underscore.... Will have a play around tonight... Cheers, Paul.