Michael Goffioul wrote > For the record, such problems are easily triggered. Consider a piece of > fortran code, compiled with 4.6.x, making a call to EXP with a complex > number. This is translated by gcc/gfortran into a call to cexp, which is > provided by libgcc, hence 4.7.x. This function returns a double complex > structure (> 8 bytes), so the fortran code and libgcc will use different > calling conventions, leading to stack corruption.
You are probably right, I have recompiled arpack, eigs.cc passed but now qr.cc it panics ! I will have to rebuild all libs but since I do not have any scripts and/or envoronment settings (it has all been done by Tatsuro) I will have to start from scratch and that will take time. Philipe, I will report and share everything when I will get some better results. Nitzan -- View this message in context: http://octave.1599824.n4.nabble.com/Octave-3-6-4-rc0-Mingw-gcc4-7-2-panics-tp4646723p4646733.html Sent from the Octave - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
