> What are the known issues with those compilers? The list is long, see
http://gcc.gnu.org/cgi-bin/gnatsweb.pl > Is the trial and error method the usual approach ? ;-) No. Instead, one needs to clearly identify the problem. If it is a compiler bug, it would fall into the class "generates bad code". A useful bug report in this category would identify a function, and present it together with the assembler code. > Given the results above is it licit to blame the compiler(s)? Not necessarily. It could be also that the program uses undefined behaviour, such as accessing an uninitialized variable. If that is a variable on stack, it might or might not crash depending on the previous value of the stack. Regards, Martin
