Re: [petsc-dev] clang warning, 64bit indices

On Wed, 9 Mar 2016, Lisandro Dalcin wrote: > On 9 March 2016 at 23:00, Satish Balay wrote: > > On Wed, 9 Mar 2016, Lisandro Dalcin wrote: > > > >> On 9 March 2016 at 22:51, Satish Balay wrote: > >> > Well the following works.. > >> > >> OK, but that's a

Re: [petsc-dev] clang warning, 64bit indices

On 9 March 2016 at 23:00, Satish Balay wrote: > On Wed, 9 Mar 2016, Lisandro Dalcin wrote: > >> On 9 March 2016 at 22:51, Satish Balay wrote: >> > Well the following works.. >> >> OK, but that's a small int, and you are little-endian, right? Could >> you try

Re: [petsc-dev] clang++ warning about C++ input with .c files

On Wed, 9 Mar 2016, Lisandro Dalcin wrote: > clang: warning: treating 'c' input as 'c++' when in C++ mode, this > behavior is deprecated > > These warnings can be silenced passing the flag "-x c++" to the compiler. > > Any downsides to consider? I think it will treat even '.o' as c++ source -

[petsc-dev] clang++ warning about C++ input with .c files

clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated These warnings can be silenced passing the flag "-x c++" to the compiler. Any downsides to consider? -- Lisandro Dalcin Research Scientist Computer, Electrical and Mathematical Sciences &

Re: [petsc-dev] clang warning, 64bit indices

On Wed, 9 Mar 2016, Lisandro Dalcin wrote: > On 9 March 2016 at 22:51, Satish Balay wrote: > > Well the following works.. > > OK, but that's a small int, and you are little-endian, right? Could > you try the following? > > char c[] = "9223372036854775807" sbalay@ps3 ~/junk

Re: [petsc-dev] clang warning, 64bit indices

On 9 March 2016 at 22:51, Satish Balay wrote: > Well the following works.. OK, but that's a small int, and you are little-endian, right? Could you try the following? char c[] = "9223372036854775807" -- Lisandro Dalcin Research Scientist Computer, Electrical

Re: [petsc-dev] clang warning, 64bit indices

On Wed, 9 Mar 2016, Lisandro Dalcin wrote: > I got the following warning using clang on Mac with 64bit indices. The > warning is legit, however fixing it as suggested might be problematic > on Window, I think we should use "%I64d" in that platform (see >

Re: [petsc-dev] [petsc-checkbuilds] PETSc blame digest (next) 2016-03-09

I switched solaris builds to use gnumake-4 - [so that --output-sync=recurse option is used] to avoid this issue. Satish On Wed, 9 Mar 2016, PETSc checkBuilds wrote: > > > Dear PETSc developer, > > This email contains listings of contributions attributed to you by > `git blame` that caused

Re: [petsc-dev] PETSc release soon, request for input on needed fixes or enhancements

On 09/03/16 15:37, Barry Smith wrote: > >> On Mar 9, 2016, at 8:37 AM, Lawrence Mitchell >> wrote: >> >> Hi Barry, >> >> On 27/02/16 20:36, Barry Smith wrote: >>> >>> PETSc Users, >>> >>>We are planning the PETSc release 3.7 shortly. If you know of any

Re: [petsc-dev] PETSc release soon, request for input on needed fixes or enhancements

> On Mar 9, 2016, at 8:37 AM, Lawrence Mitchell > wrote: > > Hi Barry, > > On 27/02/16 20:36, Barry Smith wrote: >> >> PETSc Users, >> >>We are planning the PETSc release 3.7 shortly. If you know of any bugs >> that need to be fixed or enhancements

Re: [petsc-dev] PETSc release soon, request for input on needed fixes or enhancements

Hi, the make install error occurred again last night, but with a different error: CC arch-linux2-c-debug/obj/src/tao/leastsquares/impls/pounders/gqt.o CLINKER

[petsc-dev] CFP MIS Journal - Special Issue on: Adaptive Mobile Crowd Sensing Security for BYOD Convergence in Mobile Creative Research

Mobile Information Systems Journal Special Issue on: Adaptive Mobile Crowd Sensing Security for BYOD Convergence in Mobile Creative Research http://www.hindawi.com/journals/MISY/si/981208/cfp/ Call for Papers: Recent advances in pervasive computers, networks, telecommunication, and ICT