This piece of code does stress compilers in complex/optimized mode. When I tried previously - I couldn't reproduce the problem [with VS2012]
Now - when was trying out something else - I see the breakage. But subsequent invocation of the compiler went through fine. [without any code changes] Appears to be a bug in the compiler triggered randomly. Note: configure defautls to -O2 for this compiler for --debugging=0 Satish On Sun, 26 May 2013, Agnostic Noname wrote: > Dear Matt and Satish, > > thank you for the immediate reply. I tried looking around for any updates > to VS2012 but I didn't find any. However, adding > #include <petscerror.h> > to src\mat\impls\baij\seq\baijfact2.c did the trick. Although the make test > failed, the petsc libs generated were libf2cblas.lib, libf2clapack.lib > and libpetsc.lib so I think it should be ok. > Hopefully I will manage to link them to my application. > I know it's an ugly hack but most of my colleagues that will try to compile > petsc will be using VS2012. I don't know the reason for this error, since > in mac and linux petsc works like a charm. > > Thanks again for your help. It's greatly appreciated. > > > > On Sun, May 26, 2013 at 5:33 AM, Satish Balay <[email protected]> wrote: > > > On Sat, 25 May 2013, Matthew Knepley wrote: > > > > > On Sat, May 25, 2013 at 6:27 AM, Agnostic Noname <[email protected]> > > wrote: > > > > > > > > > 1) Please send messages with logs to [email protected] so everyone > > > does not get huge attachments > > > > Its now acceptable to send build logs to petsc-users. petsc-users is > > now support with public archives - and petsc-maint is as usualy > > private communiation. > > > > We should be doing automatic compression of attachments [which we > > haven't figured out]. Currently the limit is set at 5MB - so if the > > e-mail comes through - then its acceptable. Alternative is to compress > > and send logs [or we generate logs in a compressed-ready-to-send > > tarball] > > > > Satish > > >
