From: Sam S. <sd...@gn...> - 2009-01-12 22:47:40
|
Vladimir Tzankov wrote: > On Jan 11, 2009, at 9:13 PM, Richard Stallman wrote: >> >> Is this a bug in GCC, or is it a bug in CLISP? > > With 32 bit x86/ppc versions I do not observe anything wrong. > Sam has observed problems - probably with 64 bit x86. Sam? these is no doubt that this is a GCC platform-specific bug. this conclusion is based on the following facts: 1. gcc3 & gcc4 compile clisp on i386 and x86_64 fine. 2. gcc3.2 compiles clisp on sparc fine. 3. gcc3.3 and 4* does NOT compile clisp on sparc: random errors happen by replacing object files compiled by gcc3.2 and 3.3 in the final linking, one can identify the C file which gcc3.3 fails to compile correctly. the file is huge, has many static functions, and thus resists splitting. diffing assembly is no help: the diffs are HUGE. >> If it is a bug in GCC, please file a GCC bug report so that it can get >> fixed. > > If I can reproduce it will try to isolate it and file a bug report. the problem is that GCC maintainers want a small example which clearly displays the bug. producing that requires non-trivial knowledge of assembly which I do not possess. |