I've had similar happen to me when turning on optimization _and_ debugging with the Intel Compiler. Maybe you should try turning off optimization and see if it generates correct code then... Derek
On Mon, Oct 19, 2009 at 8:47 AM, Petry Stefan <[email protected]> wrote: > > ________________________________________ > Von: Petry Stefan > Gesendet: Dienstag, 13. Oktober 2009 15:23 > An: Roy Stogner > Betreff: AW: [Libmesh-users] libmesh and windows > > Hello again, > > we´re still trying to run example3 on windows. I found out, that we got a > wrong return value in function n_shape_functions() in file fe.h! Inside this > implementation, function n_dofs() is called. Our problem is, that n_dofs() > of file fe_xyz.C and not of file fe_lagrange.C is called. > Dim has value 2, T has value 0 (for LAGRANGE). That´s allways right. > > So our idea is, that there could be a flag for GCC, which should be set to > cause scope-operator :: to call function n_dofs() from file fe_lagrange.C... > Does anybody know something about that? > > Best regards, > Stefan > > ________________________________________ > Von: Roy Stogner [[email protected]] > Gesendet: Montag, 12. Oktober 2009 05:53 > An: Petry Stefan > Cc: [email protected] > Betreff: Re: [Libmesh-users] libmesh and windows > > On Sat, 10 Oct 2009, Petry Stefan wrote: > > > I have some questions concerning the use of libMesh on Windows. In > > another thread Roy told me that you got libMesh to compile with > > Cygwin on Windows. Is this port publicly available? > > Not a port; I used the existing version, as of... summer 2007? Cygwin > certainly isn't perfect, but it worked well enough that I don't > recall having to change any libMesh code to get it to compile with > the Laspack solver. > > Sorry I can't help you on the rest of your questions. My own > libMesh-on-Windows experience was just a way of getting some work done > when I was often stuck offline with a Windows-only laptop. I never > tried to link to non-Cygwin programs or tested performance, and I > didn't encounter any compiler bugs, certainly nothing as serious as > QUADs failing to work! > > I'd suggest trying a newer gcc (MinGW appears to have done a release > based on gcc 4.4 this summer?) and/or the newest libMesh (we released > 0.6.4-rc1 last week) just to see if either fixes things for you. > --- > Roy > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
