From: Paulo C. <pco...@ue...> - 2008-05-28 14:07:45
|
I get a lot of error messages like this `.gnu.linkonce.t.__CPR117__n_dofs__53FE__tm__43_XCUiL_1_3XCQ2_12libMeshEnums8FEFamilyL_1_0SFQ2_J35J8ElemTypeQ2_J35J5Order_Ui' referenced in section `.text' of src/fe/fe_xyz.x86_64-unknown-linux-gnu.opt.o: defined in discarded section `.gnu.linkonce.t.__CPR117__n_dofs__53FE__tm__43_XCUiL_1_3XCQ2_12libMeshEnums8FEFamilyL_1_0SFQ2_J35J8ElemTypeQ2_J35J5Order_Ui' of src/fe/fe_xyz.x86_64-unknown-linux-gnu.opt.o when compiling on a 64 bit machine. How to solve this problem? Thanks in advance, Paulo |
From: Manav B. <bha...@gm...> - 2013-10-25 22:17:17
|
Hi, I am getting the following error while compiling the latest from git. I am using Apple’s clang++ 5.0 on OS X 10.9. Has anyone else seen this? Thanks, Manav CXX src/solvers/libmesh_dbg_la-petsc_dm_nonlinear_solver.lo CXX src/solvers/libmesh_dbg_la-petsc_linear_solver.lo src/solvers/petsc_diff_solver.C:65:25: error: no matching constructor for initialization of 'PetscVector<Number>' PetscVector<Number> delta_u(petsc_delta_u); ^ ~~~~~~~~~~~~~ ./include/libmesh/petsc_vector.h:61:7: note: candidate constructor (the implicit copy constructor) not viable: cannot convert argument of incomplete type 'Vec' (aka '_p_Vec *') to 'const libMesh::PetscVector<double>' class PetscVector : public NumericVector<T> ^ ./include/libmesh/petsc_vector.h:69:3: note: candidate constructor not viable: cannot convert argument of incomplete type 'Vec' (aka '_p_Vec *') to 'const Parallel::Communicator' PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:76:3: note: candidate constructor not viable: requires at least 2 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:84:3: note: candidate constructor not viable: requires at least 3 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:94:3: note: candidate constructor not viable: requires at least 4 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:107:3: note: candidate constructor not viable: requires 2 arguments, but 1 was provided PetscVector(Vec v, ^ src/solvers/petsc_diff_solver.C:71:25: error: no matching constructor for initialization of 'PetscVector<Number>' PetscVector<Number> u(petsc_u); ^ ~~~~~~~ ./include/libmesh/petsc_vector.h:61:7: note: candidate constructor (the implicit copy constructor) not viable: cannot convert argument of incomplete type 'Vec' (aka '_p_Vec *') to 'const libMesh::PetscVector<double>' class PetscVector : public NumericVector<T> ^ ./include/libmesh/petsc_vector.h:69:3: note: candidate constructor not viable: cannot convert argument of incomplete type 'Vec' (aka '_p_Vec *') to 'const Parallel::Communicator' PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:76:3: note: candidate constructor not viable: requires at least 2 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:84:3: note: candidate constructor not viable: requires at least 3 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:94:3: note: candidate constructor not viable: requires at least 4 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:107:3: note: candidate constructor not viable: requires 2 arguments, but 1 was provided PetscVector(Vec v, ^ src/solvers/petsc_diff_solver.C:77:25: error: no matching constructor for initialization of 'PetscVector<Number>' PetscVector<Number> res(petsc_res); ^ ~~~~~~~~~ ./include/libmesh/petsc_vector.h:61:7: note: candidate constructor (the implicit copy constructor) not viable: cannot convert argument of incomplete type 'Vec' (aka '_p_Vec *') to 'const libMesh::PetscVector<double>' class PetscVector : public NumericVector<T> ^ ./include/libmesh/petsc_vector.h:69:3: note: candidate constructor not viable: cannot convert argument of incomplete type 'Vec' (aka '_p_Vec *') to 'const Parallel::Communicator' PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:76:3: note: candidate constructor not viable: requires at least 2 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:84:3: note: candidate constructor not viable: requires at least 3 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:94:3: note: candidate constructor not viable: requires at least 4 arguments, but 1 was provided PetscVector (const Parallel::Communicator &comm, ^ ./include/libmesh/petsc_vector.h:107:3: note: candidate constructor not viable: requires 2 arguments, but 1 was provided PetscVector(Vec v, ^ 3 errors generated. make[1]: *** [src/solvers/libmesh_dbg_la-petsc_diff_solver.lo] Error 1 make[1]: *** Waiting for unfinished jobs.... make: *** [all-recursive] Error 1 Air:libmesh manav$ less .git/config Air:libmesh manav$ cp config_options ~/libmesh/ |
From: John P. <jwp...@gm...> - 2013-10-25 22:40:39
|
On Fri, Oct 25, 2013 at 4:17 PM, Manav Bhatia <bha...@gm...> wrote: > Hi, > > I am getting the following error while compiling the latest from git. I > am using Apple’s clang++ 5.0 on OS X 10.9. > > Has anyone else seen this? > Nope. Are you possibly compiling libmesh with complex enabled, but you don't have a PETSc with complex enabled? -- John |
From: Manav B. <bha...@gm...> - 2013-10-25 22:44:10
|
No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. I will dig a bit more to see if I can figure something out. Will keep you posted. -Manav On Oct 25, 2013, at 6:40 PM, John Peterson <jwp...@gm...> wrote: > > > > On Fri, Oct 25, 2013 at 4:17 PM, Manav Bhatia <bha...@gm...> wrote: > Hi, > > I am getting the following error while compiling the latest from git. I > am using Apple’s clang++ 5.0 on OS X 10.9. > > Has anyone else seen this? > > Nope. Are you possibly compiling libmesh with complex enabled, but you don't have a PETSc with complex enabled? > > -- > John |
From: John P. <jwp...@gm...> - 2013-10-25 22:47:24
|
On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > No, everything is real valued. I updated to the latest OS couple of days > ago, and this morning did "git pull”, followed by make. > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. -- John |
From: Manav B. <bha...@gm...> - 2013-10-25 23:35:07
|
It seems like this compilation error was introduced with the monitor updates. I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. -Manav On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > -- > John |
From: subramanya s. <po...@ou...> - 2013-10-26 01:57:45
|
I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya > From: bha...@gm... > Date: Fri, 25 Oct 2013 19:34:58 -0400 > To: jwp...@gm... > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > It seems like this compilation error was introduced with the monitor updates. > > I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. > > adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. > > -Manav > > > On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > > > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > > > > -- > > John > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Manav B. <bha...@gm...> - 2013-10-27 01:34:58
|
Hi Subramanya, Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. Manav On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote: > I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes? > Subramanya > > > From: bha...@gm... > > Date: Fri, 25 Oct 2013 19:34:58 -0400 > > To: jwp...@gm... > > CC: lib...@li... > > Subject: Re: [Libmesh-users] compiling error > > > > It seems like this compilation error was introduced with the monitor updates. > > > > I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. > > > > adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. > > > > -Manav > > > > > > On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > > > > > > > > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > > > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > > > > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > > > > > > > -- > > > John > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > _______________________________________________ > > Libmesh-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: subramanya s. <po...@ou...> - 2013-10-27 03:25:07
|
Hi Manav, I see what you mean. With clang 5.0, getpot is failing. all the parameters are getting set to the default value. Thanks, Subramanya Subject: Re: [Libmesh-users] compiling error From: bha...@gm... Date: Sat, 26 Oct 2013 21:34:48 -0400 CC: jwp...@gm...; lib...@li... To: po...@ou... Hi Subramanya, Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. Manav On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote:I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya > From: bha...@gm... > Date: Fri, 25 Oct 2013 19:34:58 -0400 > To: jwp...@gm... > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > It seems like this compilation error was introduced with the monitor updates. > > I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. > > adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. > > -Manav > > > On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > > > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > > > > -- > > John > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: subramanya s. <po...@ou...> - 2013-10-27 03:30:29
|
GetPot::print() (for the appropriate object) is printing blank lines. This is with code that was working with gcc 4.8 (macports) version. > From: po...@ou... > To: bha...@gm... > Date: Sat, 26 Oct 2013 23:24:59 -0400 > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > Hi Manav, I see what you mean. With clang 5.0, getpot is failing. all the parameters are getting set to the default value. Thanks, Subramanya > Subject: Re: [Libmesh-users] compiling error > From: bha...@gm... > Date: Sat, 26 Oct 2013 21:34:48 -0400 > CC: jwp...@gm...; lib...@li... > To: po...@ou... > > Hi Subramanya, > Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. > Manav > On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote:I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya > > > From: bha...@gm... > > Date: Fri, 25 Oct 2013 19:34:58 -0400 > > To: jwp...@gm... > > CC: lib...@li... > > Subject: Re: [Libmesh-users] compiling error > > > > It seems like this compilation error was introduced with the monitor updates. > > > > I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. > > > > adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. > > > > -Manav > > > > > > On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > > > > > > > > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > > > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > > > > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > > > > > > > -- > > > John > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > _______________________________________________ > > Libmesh-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libmesh-users > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Manav B. <bha...@gm...> - 2013-10-27 04:36:22
|
Good to know about this! I did a bit of digging into it, and the problem seems to be coming after the call to istr.unget() at line 990 in GetPot::_skip_whitespace(). For some reason, it seems to corrupt the istream data structure so that std::cout << istr prints false. Using istream::unget() seems to work OK outside of GetPot. Also, I downloaded GetPot from its website and get the same issue. I do not know why this is happening. Perhaps a bug with clang 5, or maybe something about how GetPot does things. -Manav On Oct 26, 2013, at 11:30 PM, subramanya sadasiva <po...@ou...> wrote: > GetPot::print() (for the appropriate object) is printing blank lines. This is with code that was working with gcc 4.8 (macports) version. > > > > From: po...@ou... > > To: bha...@gm... > > Date: Sat, 26 Oct 2013 23:24:59 -0400 > > CC: lib...@li... > > Subject: Re: [Libmesh-users] compiling error > > > > Hi Manav, I see what you mean. With clang 5.0, getpot is failing. all the parameters are getting set to the default value. Thanks, Subramanya > > Subject: Re: [Libmesh-users] compiling error > > From: bha...@gm... > > Date: Sat, 26 Oct 2013 21:34:48 -0400 > > CC: jwp...@gm...; lib...@li... > > To: po...@ou... > > > > Hi Subramanya, > > Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. > > Manav > > On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote:I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya > > > > > From: bha...@gm... > > > Date: Fri, 25 Oct 2013 19:34:58 -0400 > > > To: jwp...@gm... > > > CC: lib...@li... > > > Subject: Re: [Libmesh-users] compiling error > > > > > > It seems like this compilation error was introduced with the monitor updates. > > > > > > I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. > > > > > > adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. > > > > > > -Manav > > > > > > > > > On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > > > > > > > > > > > > > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > > > > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > > > > > > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > > > > > > > > > > -- > > > > John > > > > > > ------------------------------------------------------------------------------ > > > October Webinars: Code for Performance > > > Free Intel webinars can help you accelerate application performance. > > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > > the latest Intel processors and coprocessors. See abstracts and register > > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > > _______________________________________________ > > > Libmesh-users mailing list > > > Lib...@li... > > > https://lists.sourceforge.net/lists/listinfo/libmesh-users > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > _______________________________________________ > > Libmesh-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: subramanya s. <po...@ou...> - 2013-10-27 04:49:59
|
I localized the problem to roughly the same location. This is a bit sad, because it is just so much nicer working with clang than with gcc.. Subject: Re: [Libmesh-users] compiling error From: bha...@gm... Date: Sun, 27 Oct 2013 00:36:13 -0400 CC: lib...@li... To: po...@ou... Good to know about this! I did a bit of digging into it, and the problem seems to be coming after the call to istr.unget() at line 990 in GetPot::_skip_whitespace(). For some reason, it seems to corrupt the istream data structure so that std::cout << istr prints false. Using istream::unget() seems to work OK outside of GetPot. Also, I downloaded GetPot from its website and get the same issue. I do not know why this is happening. Perhaps a bug with clang 5, or maybe something about how GetPot does things. -Manav On Oct 26, 2013, at 11:30 PM, subramanya sadasiva <po...@ou...> wrote:GetPot::print() (for the appropriate object) is printing blank lines. This is with code that was working with gcc 4.8 (macports) version. > From: po...@ou... > To: bha...@gm... > Date: Sat, 26 Oct 2013 23:24:59 -0400 > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > Hi Manav, I see what you mean. With clang 5.0, getpot is failing. all the parameters are getting set to the default value. Thanks, Subramanya > Subject: Re: [Libmesh-users] compiling error > From: bha...@gm... > Date: Sat, 26 Oct 2013 21:34:48 -0400 > CC: jwp...@gm...; lib...@li... > To: po...@ou... > > Hi Subramanya, > Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. > Manav > On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote:I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya > > > From: bha...@gm... > > Date: Fri, 25 Oct 2013 19:34:58 -0400 > > To: jwp...@gm... > > CC: lib...@li... > > Subject: Re: [Libmesh-users] compiling error > > > > It seems like this compilation error was introduced with the monitor updates. > > > > I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. > > > > adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. > > > > -Manav > > > > > > On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: > > > > > > > > > > > > > > On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: > > > No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. > > > > > > I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. > > > > > > > > > -- > > > John > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > _______________________________________________ > > Libmesh-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libmesh-users > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Cody P. <cod...@gm...> - 2013-10-27 16:24:40
|
I doubt it's a bug in clang. In our experience, clang had been a superior compiler to GCC in every way for a few years now catching many things that GCC does not. With OS X 10.9 John's already seen a few things "break" but in both cases it wasn't the compiler, it was long standing bugs that got fixed with the new OS (one issue with XDA, and another with NetCDF). In fact, GCC is no longer being shipped with OS X! Chances are that Getpot is doing something wrong and well just have to continue digging to find it. Oh the joy of being an early adopter. :-) Don't give up yet! Cody Sent from my iPhone > On Oct 26, 2013, at 10:50 PM, subramanya sadasiva <po...@ou...> wrote: > > I localized the problem to roughly the same location. This is a bit sad, because it is just so much nicer working with clang than with gcc.. > Subject: Re: [Libmesh-users] compiling error > From: bha...@gm... > Date: Sun, 27 Oct 2013 00:36:13 -0400 > CC: lib...@li... > To: po...@ou... > > Good to know about this! > I did a bit of digging into it, and the problem seems to be coming after the call to istr.unget() at line 990 in GetPot::_skip_whitespace(). For some reason, it seems to corrupt the istream data structure so that std::cout << istr prints false. > Using istream::unget() seems to work OK outside of GetPot. Also, I downloaded GetPot from its website and get the same issue. > I do not know why this is happening. Perhaps a bug with clang 5, or maybe something about how GetPot does things. > -Manav > > > On Oct 26, 2013, at 11:30 PM, subramanya sadasiva <po...@ou...> wrote:GetPot::print() (for the appropriate object) is printing blank lines. This is with code that was working with gcc 4.8 (macports) version. > >> From: po...@ou... >> To: bha...@gm... >> Date: Sat, 26 Oct 2013 23:24:59 -0400 >> CC: lib...@li... >> Subject: Re: [Libmesh-users] compiling error >> >> Hi Manav, I see what you mean. With clang 5.0, getpot is failing. all the parameters are getting set to the default value. Thanks, Subramanya >> Subject: Re: [Libmesh-users] compiling error >> From: bha...@gm... >> Date: Sat, 26 Oct 2013 21:34:48 -0400 >> CC: jwp...@gm...; lib...@li... >> To: po...@ou... >> >> Hi Subramanya, >> Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. >> Manav >> On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote:I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya >> >>> From: bha...@gm... >>> Date: Fri, 25 Oct 2013 19:34:58 -0400 >>> To: jwp...@gm... >>> CC: lib...@li... >>> Subject: Re: [Libmesh-users] compiling error >>> >>> It seems like this compilation error was introduced with the monitor updates. >>> >>> I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. >>> >>> adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. >>> >>> -Manav >>> >>> >>>> On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: >>>> >>>> >>>> >>>> >>>> On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: >>>> No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. >>>> >>>> I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. >>>> >>>> >>>> -- >>>> John >>> >>> ------------------------------------------------------------------------------ >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>> the latest Intel processors and coprocessors. See abstracts and register > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Libmesh-users mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk >> _______________________________________________ >> Libmesh-users mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libmesh-users > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Manav B. <bha...@gm...> - 2013-10-27 16:39:23
|
:-) Thanks, Cody. Good to know that you find clang 5 more dependable. I will spend some more time with it, but I am also kicking myself for putting myself in this situation (early adopters). Will keep you posted. -Manav On Oct 27, 2013, at 12:24 PM, Cody Permann <cod...@gm...> wrote: > I doubt it's a bug in clang. In our experience, clang had been a > superior compiler to GCC in every way for a few years now catching > many things that GCC does not. With OS X 10.9 John's already seen a > few things "break" but in both cases it wasn't the compiler, it was > long standing bugs that got fixed with the new OS (one issue with XDA, > and another with NetCDF). In fact, GCC is no longer being shipped > with OS X! Chances are that Getpot is doing something wrong and well > just have to continue digging to find it. Oh the joy of being an > early adopter. :-) > > Don't give up yet! > Cody > > Sent from my iPhone > >> On Oct 26, 2013, at 10:50 PM, subramanya sadasiva <po...@ou...> wrote: >> >> I localized the problem to roughly the same location. This is a bit sad, because it is just so much nicer working with clang than with gcc.. >> Subject: Re: [Libmesh-users] compiling error >> From: bha...@gm... >> Date: Sun, 27 Oct 2013 00:36:13 -0400 >> CC: lib...@li... >> To: po...@ou... >> >> Good to know about this! >> I did a bit of digging into it, and the problem seems to be coming after the call to istr.unget() at line 990 in GetPot::_skip_whitespace(). For some reason, it seems to corrupt the istream data structure so that std::cout << istr prints false. >> Using istream::unget() seems to work OK outside of GetPot. Also, I downloaded GetPot from its website and get the same issue. >> I do not know why this is happening. Perhaps a bug with clang 5, or maybe something about how GetPot does things. >> -Manav >> >> >> On Oct 26, 2013, at 11:30 PM, subramanya sadasiva <po...@ou...> wrote:GetPot::print() (for the appropriate object) is printing blank lines. This is with code that was working with gcc 4.8 (macports) version. >> >>> From: po...@ou... >>> To: bha...@gm... >>> Date: Sat, 26 Oct 2013 23:24:59 -0400 >>> CC: lib...@li... >>> Subject: Re: [Libmesh-users] compiling error >>> >>> Hi Manav, I see what you mean. With clang 5.0, getpot is failing. all the parameters are getting set to the default value. Thanks, Subramanya >>> Subject: Re: [Libmesh-users] compiling error >>> From: bha...@gm... >>> Date: Sat, 26 Oct 2013 21:34:48 -0400 >>> CC: jwp...@gm...; lib...@li... >>> To: po...@ou... >>> >>> Hi Subramanya, >>> Thanks for sharing this. What compiler are you using? Is it clang? If so, what is your experience using getpot? It is unable to extract any parameters from my input files when compiled with clang 5, but I see no problems with g++-4.8 from macports. >>> Manav >>> On Oct 25, 2013, at 9:57 PM, subramanya sadasiva <po...@ou...> wrote:I was just able to compile with clang on OS X 10.9 with no problems. Were you guys able to push the changes?Subramanya >>> >>>> From: bha...@gm... >>>> Date: Fri, 25 Oct 2013 19:34:58 -0400 >>>> To: jwp...@gm... >>>> CC: lib...@li... >>>> Subject: Re: [Libmesh-users] compiling error >>>> >>>> It seems like this compilation error was introduced with the monitor updates. >>>> >>>> I am compiling with disable-default-comm-world, with which the petsc vector constructor is expecting a second argument. >>>> >>>> adding a second argument of "solver.comm()" to the instantiation of PetscVector at lines 65, 71 and 77 in petsc_diff_solver.C allows the code to compile without issues. >>>> >>>> -Manav >>>> >>>> >>>>> On Oct 25, 2013, at 6:46 PM, John Peterson <jwp...@gm...> wrote: >>>>> >>>>> >>>>> >>>>> >>>>> On Fri, Oct 25, 2013 at 4:43 PM, Manav Bhatia <bha...@gm...> wrote: >>>>> No, everything is real valued. I updated to the latest OS couple of days ago, and this morning did "git pull”, followed by make. >>>>> >>>>> I'd definitely blow away any old build directories and rerun configure if you upgraded your OS... but maybe you did that already. >>>>> >>>>> >>>>> -- >>>>> John >>>> >>>> ------------------------------------------------------------------------------ >>>> October Webinars: Code for Performance >>>> Free Intel webinars can help you accelerate application performance. >>>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>>> the latest Intel processors and coprocessors. See abstracts and register > >>>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk >>>> _______________________________________________ >>>> Libmesh-users mailing list >>>> Lib...@li... >>>> https://lists.sourceforge.net/lists/listinfo/libmesh-users >>> >>> ------------------------------------------------------------------------------ >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>> the latest Intel processors and coprocessors. See abstracts and register > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Libmesh-users mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users >> >> ------------------------------------------------------------------------------ >> October Webinars: Code for Performance >> Free Intel webinars can help you accelerate application performance. >> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >> the latest Intel processors and coprocessors. See abstracts and register > >> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk >> _______________________________________________ >> Libmesh-users mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Roy S. <roy...@ic...> - 2013-10-27 16:47:09
|
On Sun, 27 Oct 2013, Cody Permann wrote: > Chances are that Getpot is doing something wrong and well just have > to continue digging to find it. Oh the joy of being an early > adopter. :-) Has anyone tried clang 5.0 on Linux to see if the problem is reproduceable there? I do occasional testing with clang but it looks like I'm using 3.5, which I suppose is ancient by LLVM standards. --- Roy |
From: Roy S. <roy...@ic...> - 2013-10-27 16:49:06
|
On Sun, 27 Oct 2013, Roy Stogner wrote: > On Sun, 27 Oct 2013, Cody Permann wrote: > >> Chances are that Getpot is doing something wrong and well just have >> to continue digging to find it. Oh the joy of being an early >> adopter. :-) > > Has anyone tried clang 5.0 on Linux to see if the problem is > reproduceable there? I do occasional testing with clang but it looks > like I'm using 3.5, which I suppose is ancient by LLVM standards. I meant to type 3.2... which actually *doesn't* look that ancient. http://llvm.org/releases/ lists 3.3 as their latest release, in June. Is "clang 5" some Mac-specific fork? --- Roy |
From: Manav B. <bha...@gm...> - 2013-10-27 16:50:58
|
It is based on LLVM 3.3svn. Following is the output of clang —version Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) -Manav On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: > > On Sun, 27 Oct 2013, Roy Stogner wrote: > >> On Sun, 27 Oct 2013, Cody Permann wrote: >> >>> Chances are that Getpot is doing something wrong and well just have >>> to continue digging to find it. Oh the joy of being an early >>> adopter. :-) >> >> Has anyone tried clang 5.0 on Linux to see if the problem is >> reproduceable there? I do occasional testing with clang but it looks >> like I'm using 3.5, which I suppose is ancient by LLVM standards. > > I meant to type 3.2... which actually *doesn't* look that ancient. > > http://llvm.org/releases/ lists 3.3 as their latest release, in June. > Is "clang 5" some Mac-specific fork? > --- > Roy > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Cody P. <cod...@gm...> - 2013-10-27 17:46:18
|
We have a few test systems setup at work. Either myself or John can dig in early next week to get to the bottom of it. Cody Sent from my evil iPad On Oct 27, 2013, at 10:50 AM, Manav Bhatia <bha...@gm...> wrote: It is based on LLVM 3.3svn. Following is the output of clang —version Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) -Manav On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: On Sun, 27 Oct 2013, Roy Stogner wrote: On Sun, 27 Oct 2013, Cody Permann wrote: Chances are that Getpot is doing something wrong and well just have to continue digging to find it. Oh the joy of being an early adopter. :-) Has anyone tried clang 5.0 on Linux to see if the problem is reproduceable there? I do occasional testing with clang but it looks like I'm using 3.5, which I suppose is ancient by LLVM standards. I meant to type 3.2... which actually *doesn't* look that ancient. http://llvm.org/releases/ lists 3.3 as their latest release, in June. Is "clang 5" some Mac-specific fork? --- Roy ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list Lib...@li... https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Manav B. <bha...@gm...> - 2013-10-27 22:50:12
|
I had sent an email to the developer of GetPot describing the situation. He has an updated version of the code that he has been working on, but he is yet to release it on his website. He shared it with me and it works without any problems with clang5. I have not tried to look at what might be the modification in this update. In any case, I have requested him to release the code, and perhaps it will be a good idea to include that update in libMesh. -Manav On Oct 27, 2013, at 1:46 PM, Cody Permann <cod...@gm...> wrote: > We have a few test systems setup at work. Either myself or John can dig in early next week to get to the bottom of it. > > Cody > > Sent from my evil iPad > > On Oct 27, 2013, at 10:50 AM, Manav Bhatia <bha...@gm...> wrote: > >> It is based on LLVM 3.3svn. Following is the output of clang —version >> >> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) >> >> -Manav >> >> >> On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: >> >>> >>> On Sun, 27 Oct 2013, Roy Stogner wrote: >>> >>>> On Sun, 27 Oct 2013, Cody Permann wrote: >>>> >>>>> Chances are that Getpot is doing something wrong and well just have >>>>> to continue digging to find it. Oh the joy of being an early >>>>> adopter. :-) >>>> >>>> Has anyone tried clang 5.0 on Linux to see if the problem is >>>> reproduceable there? I do occasional testing with clang but it looks >>>> like I'm using 3.5, which I suppose is ancient by LLVM standards. >>> >>> I meant to type 3.2... which actually *doesn't* look that ancient. >>> >>> http://llvm.org/releases/ lists 3.3 as their latest release, in June. >>> Is "clang 5" some Mac-specific fork? >>> --- >>> Roy >>> >>> ------------------------------------------------------------------------------ >>> October Webinars: Code for Performance >>> Free Intel webinars can help you accelerate application performance. >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from >>> the latest Intel processors and coprocessors. See abstracts and register > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Libmesh-users mailing list >>> Lib...@li... >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users >> |
From: John P. <jwp...@gm...> - 2013-10-28 15:55:14
|
On Sun, Oct 27, 2013 at 4:50 PM, Manav Bhatia <bha...@gm...> wrote: > I had sent an email to the developer of GetPot describing the situation. > He has an updated version of the code that he has been working on, but he > is yet to release it on his website. He shared it with me and it works > without any problems with clang5. I have not tried to look at what might be > the modification in this update. > The main difference between the libmesh and "upstream" versions of the code (at least, around the lines you mentioned) seems to be that Roy commented out a few lines in the libmesh version: // RHS: Why is this here? It breaks on empty comments // tmp = istr.get(); // if( ! istr ) { istr.unget(); return; } By the way, the error manifests itself for me on Apple clang in adjoints_ex3, where "domainfile" retains its default value of "mesh.xda" rather than getting the appropriate value of 'H_channel_quads.xda' from the input file. Do you have a smaller test case that reliably produces the error? -- John |
From: subramanya s. <po...@ou...> - 2013-10-27 22:53:06
|
Hi manav, is it possible for you to send the modified version of getpot? Thanks, Subramanya > From: bha...@gm... > Date: Sun, 27 Oct 2013 18:50:01 -0400 > To: cod...@gm... > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > I had sent an email to the developer of GetPot describing the situation. He has an updated version of the code that he has been working on, but he is yet to release it on his website. He shared it with me and it works without any problems with clang5. I have not tried to look at what might be the modification in this update. > > In any case, I have requested him to release the code, and perhaps it will be a good idea to include that update in libMesh. > > -Manav > > > On Oct 27, 2013, at 1:46 PM, Cody Permann <cod...@gm...> wrote: > > > We have a few test systems setup at work. Either myself or John can dig in early next week to get to the bottom of it. > > > > Cody > > > > Sent from my evil iPad > > > > On Oct 27, 2013, at 10:50 AM, Manav Bhatia <bha...@gm...> wrote: > > > >> It is based on LLVM 3.3svn. Following is the output of clang —version > >> > >> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) > >> > >> -Manav > >> > >> > >> On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: > >> > >>> > >>> On Sun, 27 Oct 2013, Roy Stogner wrote: > >>> > >>>> On Sun, 27 Oct 2013, Cody Permann wrote: > >>>> > >>>>> Chances are that Getpot is doing something wrong and well just have > >>>>> to continue digging to find it. Oh the joy of being an early > >>>>> adopter. :-) > >>>> > >>>> Has anyone tried clang 5.0 on Linux to see if the problem is > >>>> reproduceable there? I do occasional testing with clang but it looks > >>>> like I'm using 3.5, which I suppose is ancient by LLVM standards. > >>> > >>> I meant to type 3.2... which actually *doesn't* look that ancient. > >>> > >>> http://llvm.org/releases/ lists 3.3 as their latest release, in June. > >>> Is "clang 5" some Mac-specific fork? > >>> --- > >>> Roy > >>> > >>> ------------------------------------------------------------------------------ > >>> October Webinars: Code for Performance > >>> Free Intel webinars can help you accelerate application performance. > >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > >>> the latest Intel processors and coprocessors. See abstracts and register > > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > >>> _______________________________________________ > >>> Libmesh-users mailing list > >>> Lib...@li... > >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users > >> > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: Roy S. <roy...@ic...> - 2013-10-28 12:03:19
|
On Sun, 27 Oct 2013, subramanya sadasiva wrote: >> In any case, I have requested him to release the code, and perhaps >> it will be a good idea to include that update in libMesh. A good idea, but probably not a possible idea. We had to fork GetPot from quite a few versions back after discovering that the latest versions were no longer being released under an open source license. --- Roy |
From: Manav B. <bha...@gm...> - 2013-10-27 22:59:41
|
Hi Subramanya, This is not my code, so I do not want to send out unreleased versions without the permission of the author. I’d rather the developer send out the update. I will also send him an email to seek his permission for sharing, and see what he says. -Manav On Oct 27, 2013, at 6:52 PM, subramanya sadasiva <po...@ou...> wrote: > Hi manav, > is it possible for you to send the modified version of getpot? > Thanks, > Subramanya > > > > From: bha...@gm... > > Date: Sun, 27 Oct 2013 18:50:01 -0400 > > To: cod...@gm... > > CC: lib...@li... > > Subject: Re: [Libmesh-users] compiling error > > > > I had sent an email to the developer of GetPot describing the situation. He has an updated version of the code that he has been working on, but he is yet to release it on his website. He shared it with me and it works without any problems with clang5. I have not tried to look at what might be the modification in this update. > > > > In any case, I have requested him to release the code, and perhaps it will be a good idea to include that update in libMesh. > > > > -Manav > > > > > > On Oct 27, 2013, at 1:46 PM, Cody Permann <cod...@gm...> wrote: > > > > > We have a few test systems setup at work. Either myself or John can dig in early next week to get to the bottom of it. > > > > > > Cody > > > > > > Sent from my evil iPad > > > > > > On Oct 27, 2013, at 10:50 AM, Manav Bhatia <bha...@gm...> wrote: > > > > > >> It is based on LLVM 3.3svn. Following is the output of clang —version > > >> > > >> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) > > >> > > >> -Manav > > >> > > >> > > >> On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: > > >> > > >>> > > >>> On Sun, 27 Oct 2013, Roy Stogner wrote: > > >>> > > >>>> On Sun, 27 Oct 2013, Cody Permann wrote: > > >>>> > > >>>>> Chances are that Getpot is doing something wrong and well just have > > >>>>> to continue digging to find it. Oh the joy of being an early > > >>>>> adopter. :-) > > >>>> > > >>>> Has anyone tried clang 5.0 on Linux to see if the problem is > > >>>> reproduceable there? I do occasional testing with clang but it looks > > >>>> like I'm using 3.5, which I suppose is ancient by LLVM standards. > > >>> > > >>> I meant to type 3.2... which actually *doesn't* look that ancient. > > >>> > > >>> http://llvm.org/releases/ lists 3.3 as their latest release, in June. > > >>> Is "clang 5" some Mac-specific fork? > > >>> --- > > >>> Roy > > >>> > > >>> ------------------------------------------------------------------------------ > > >>> October Webinars: Code for Performance > > >>> Free Intel webinars can help you accelerate application performance. > > >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > >>> the latest Intel processors and coprocessors. See abstracts and register > > > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > >>> _______________________________________________ > > >>> Libmesh-users mailing list > > >>> Lib...@li... > > >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users > > >> > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > _______________________________________________ > > Libmesh-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: subramanya s. <po...@ou...> - 2013-10-28 04:35:19
|
I just tried clang-3.3 on a linux machine and getpot worked without any issues. This seems to be some apple specific thing. -Subramanya Subject: Re: [Libmesh-users] compiling error From: bha...@gm... Date: Sun, 27 Oct 2013 18:59:29 -0400 CC: cod...@gm...; lib...@li... To: po...@ou... Hi Subramanya, This is not my code, so I do not want to send out unreleased versions without the permission of the author. I’d rather the developer send out the update. I will also send him an email to seek his permission for sharing, and see what he says. -Manav On Oct 27, 2013, at 6:52 PM, subramanya sadasiva <po...@ou...> wrote:Hi manav, is it possible for you to send the modified version of getpot? Thanks, Subramanya > From: bha...@gm... > Date: Sun, 27 Oct 2013 18:50:01 -0400 > To: cod...@gm... > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > I had sent an email to the developer of GetPot describing the situation. He has an updated version of the code that he has been working on, but he is yet to release it on his website. He shared it with me and it works without any problems with clang5. I have not tried to look at what might be the modification in this update. > > In any case, I have requested him to release the code, and perhaps it will be a good idea to include that update in libMesh. > > -Manav > > > On Oct 27, 2013, at 1:46 PM, Cody Permann <cod...@gm...> wrote: > > > We have a few test systems setup at work. Either myself or John can dig in early next week to get to the bottom of it. > > > > Cody > > > > Sent from my evil iPad > > > > On Oct 27, 2013, at 10:50 AM, Manav Bhatia <bha...@gm...> wrote: > > > >> It is based on LLVM 3.3svn. Following is the output of clang —version > >> > >> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) > >> > >> -Manav > >> > >> > >> On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: > >> > >>> > >>> On Sun, 27 Oct 2013, Roy Stogner wrote: > >>> > >>>> On Sun, 27 Oct 2013, Cody Permann wrote: > >>>> > >>>>> Chances are that Getpot is doing something wrong and well just have > >>>>> to continue digging to find it. Oh the joy of being an early > >>>>> adopter. :-) > >>>> > >>>> Has anyone tried clang 5.0 on Linux to see if the problem is > >>>> reproduceable there? I do occasional testing with clang but it looks > >>>> like I'm using 3.5, which I suppose is ancient by LLVM standards. > >>> > >>> I meant to type 3.2... which actually *doesn't* look that ancient. > >>> > >>> http://llvm.org/releases/ lists 3.3 as their latest release, in June. > >>> Is "clang 5" some Mac-specific fork? > >>> --- > >>> Roy > >>> > >>> ------------------------------------------------------------------------------ > >>> October Webinars: Code for Performance > >>> Free Intel webinars can help you accelerate application performance. > >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > >>> the latest Intel processors and coprocessors. See abstracts and register > > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > >>> _______________________________________________ > >>> Libmesh-users mailing list > >>> Lib...@li... > >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users > >> > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |
From: subramanya s. <po...@ou...> - 2013-10-28 05:03:43
|
Hi, I just tried with the nightly build of clang (3.4) on linux to check if there were any issues with getpot, and again there were no problems with any of the examples. This seems to be an apple issue, more than a clang or getpot issue. Thanks, Subramanya > From: po...@ou... > To: bha...@gm... > Date: Mon, 28 Oct 2013 00:35:11 -0400 > CC: lib...@li... > Subject: Re: [Libmesh-users] compiling error > > I just tried clang-3.3 on a linux machine and getpot worked without any issues. This seems to be some apple specific thing. -Subramanya > > Subject: Re: [Libmesh-users] compiling error > From: bha...@gm... > Date: Sun, 27 Oct 2013 18:59:29 -0400 > CC: cod...@gm...; lib...@li... > To: po...@ou... > > Hi Subramanya, > This is not my code, so I do not want to send out unreleased versions without the permission of the author. > I’d rather the developer send out the update. I will also send him an email to seek his permission for sharing, and see what he says. -Manav > On Oct 27, 2013, at 6:52 PM, subramanya sadasiva <po...@ou...> wrote:Hi manav, is it possible for you to send the modified version of getpot? Thanks, Subramanya > > > From: bha...@gm... > > Date: Sun, 27 Oct 2013 18:50:01 -0400 > > To: cod...@gm... > > CC: lib...@li... > > Subject: Re: [Libmesh-users] compiling error > > > > I had sent an email to the developer of GetPot describing the situation. He has an updated version of the code that he has been working on, but he is yet to release it on his website. He shared it with me and it works without any problems with clang5. I have not tried to look at what might be the modification in this update. > > > > In any case, I have requested him to release the code, and perhaps it will be a good idea to include that update in libMesh. > > > > -Manav > > > > > > On Oct 27, 2013, at 1:46 PM, Cody Permann <cod...@gm...> wrote: > > > > > We have a few test systems setup at work. Either myself or John can dig in early next week to get to the bottom of it. > > > > > > Cody > > > > > > Sent from my evil iPad > > > > > > On Oct 27, 2013, at 10:50 AM, Manav Bhatia <bha...@gm...> wrote: > > > > > >> It is based on LLVM 3.3svn. Following is the output of clang —version > > >> > > >> Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn) > > >> > > >> -Manav > > >> > > >> > > >> On Oct 27, 2013, at 12:48 PM, Roy Stogner <roy...@ic...> wrote: > > >> > > >>> > > >>> On Sun, 27 Oct 2013, Roy Stogner wrote: > > >>> > > >>>> On Sun, 27 Oct 2013, Cody Permann wrote: > > >>>> > > >>>>> Chances are that Getpot is doing something wrong and well just have > > >>>>> to continue digging to find it. Oh the joy of being an early > > >>>>> adopter. :-) > > >>>> > > >>>> Has anyone tried clang 5.0 on Linux to see if the problem is > > >>>> reproduceable there? I do occasional testing with clang but it looks > > >>>> like I'm using 3.5, which I suppose is ancient by LLVM standards. > > >>> > > >>> I meant to type 3.2... which actually *doesn't* look that ancient. > > >>> > > >>> http://llvm.org/releases/ lists 3.3 as their latest release, in June. > > >>> Is "clang 5" some Mac-specific fork? > > >>> --- > > >>> Roy > > >>> > > >>> ------------------------------------------------------------------------------ > > >>> October Webinars: Code for Performance > > >>> Free Intel webinars can help you accelerate application performance. > > >>> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > >>> the latest Intel processors and coprocessors. See abstracts and register > > > >>> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > >>> _______________________________________________ > > >>> Libmesh-users mailing list > > >>> Lib...@li... > > >>> https://lists.sourceforge.net/lists/listinfo/libmesh-users > > >> > > > > ------------------------------------------------------------------------------ > > October Webinars: Code for Performance > > Free Intel webinars can help you accelerate application performance. > > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > > the latest Intel processors and coprocessors. See abstracts and register > > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > > _______________________________________________ > > Libmesh-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libmesh-users > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users |