[petsc-dev] Open solaris 64bit printf bug?

[Satish Balay]

These compilers are pretty old - we just use solaris for the
'diversity in testing' feature..

$ cc -V
cc: Sun C 5.9 SunOS_i386 Patch 124868-10 2009/04/30

There is a slightly newer version of compiler - I don't remember
why I don't use it [I suspect it had issues]

$ /opt/solarisstudio12.3/bin/cc -V
cc: Sun C 5.12 SunOS_i386 2011/11/16

I tried switching to this version to test - but the hang persisted..

Satish

On Thu, 3 Sep 2015, Barry Smith wrote:

> 
> > On Sep 3, 2015, at 10:52 PM, Satish Balay <balay at mcs.anl.gov> wrote:
> > 
> > I couldn't get this build [with 64-bit-indices] compiled in debug
> > mode. The compiler just hangs with a couple of source files.
> > 
> >          CC arch-opensolaris-misc/obj/src/mat/impls/aij/seq/inode.o
> >          CC arch-opensolaris-misc/obj/src/dm/impls/da/fdda.o
> > 
> > I had to manaully compile these sources with '-O' - instead of '-g' to
> > get the build going :(
> 
>   I noticed that same hang but wasn't bright enough to try removing the -g on them.
> 
>   We use to have trouble with compilers with optimization turned on, now we have trouble with optimization turned off!
> 
>   Barry
> 
> > 
> > Satish
> > 
> > 
> > On Thu, 3 Sep 2015, Barry Smith wrote:
> > 
> >> 
> >>  And just to annoy me I cannot get -start_in_debugger to work on that machine. Valgrind has no complaints on a Mac with the examples.
> >> 
> >>  I've found some miss-use of PetscViewerASCIIPushSynchronized() and %d in parts of plex, I don't see how they could cause this problem but I am fixing them and will push that. Maybe we'll get lucky.
> >> 
> >>  Barry
> >> 
> >>> On Sep 3, 2015, at 10:06 AM, Tobin Isaac <tisaac at ices.utexas.edu> wrote:
> >>> 
> >>> 
> >>> Here's a partial diff from http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/09/03/examples_next_arch-opensolaris-misc_n-gage.log:
> >>> 
> >>>   232c232
> >>>   <   field 0 with 2 components
> >>>   ---
> >>>> field 0 with 0 components
> >>>   234,242c234,242
> >>>   <   (   2) dim  2 offset   0 0.5 0
> >>>   <   (   3) dim  2 offset   2 1 0
> >>>   <   (   4) dim  2 offset   4 0 0.5
> >>>   <   (   5) dim  2 offset   6 0.5 0.5
> >>>   <   (   6) dim  2 offset   8 1 0.5
> >>>   <   (   7) dim  2 offset  10 0 1
> >>>   <   (   8) dim  2 offset  12 0.5 1
> >>>   <   (   9) dim  2 offset  14 0.5 0.25
> >>>   <   (  10) dim  2 offset  16 0.25 0.5
> >>>   ---
> >>>> (   2) dim  0 offset   2 0.5 0
> >>>> (   3) dim  0 offset   2 1 0
> >>>> (   4) dim  0 offset   2 0 0.5
> >>>> (   5) dim  0 offset   2 0.5 0.5
> >>>> (   6) dim  0 offset   2 1 0.5
> >>>> (   7) dim  0 offset   2 0 1
> >>>> (   8) dim  0 offset   2 0.5 1
> >>>> (   9) dim  0 offset   2 0.5 0.25
> >>>> (  10) dim  0 offset   2 0.25 0.5
> >>> 
> >>> The numbers that printf is making 0 (or 2) clearly aren't, because
> >>> they are used to iterate over a section and display its contents.  But
> >>> other PetscInt's are printed fine elsewhere.  Weird.
> >>> 
> >>> Toby
> >>> 
> >> 
> >> 
> > 
> 
>