"platforms/opencl/include/OpenCLEvent.h" did not exist on "74a8266f4fbe2ac74c41ef84b47b57245e729020"
- 13 Apr, 2020 1 commit
-
-
Giacomo Fiorin authored
See https://github.com/lammps/lammps/pull/1992
-
- 12 Dec, 2019 1 commit
-
-
Jérôme Hénin authored
Lepton::ParsedExpression::getConstantValue() used to return NaN to indicate non-constant expressions. This can break with -ffast-math optimization where NaN comparisons are not defined. This patch defines bool isConstant() to test whether an expression is constant before calling getConstantValue(). getConstantValue() now throws an exception if called on a non-constant expression.
-
- 01 Jun, 2019 1 commit
-
-
peastman authored
-
- 21 Mar, 2019 1 commit
-
-
peastman authored
-
- 20 Mar, 2019 1 commit
-
-
peastman authored
-
- 23 Jul, 2018 1 commit
-
-
peastman authored
-
- 03 Jul, 2018 1 commit
-
-
peastman authored
-
- 27 Apr, 2018 1 commit
-
-
peastman authored
-
- 10 Aug, 2016 1 commit
-
-
peastman authored
-
- 25 Jul, 2016 1 commit
-
-
peastman authored
-
- 25 Apr, 2016 1 commit
-
-
peastman authored
-
- 09 Jun, 2015 1 commit
-
-
Peter Eastman authored
-
- 06 May, 2015 1 commit
-
-
peastman authored
-
- 13 Feb, 2015 2 commits
- 06 Feb, 2015 1 commit
-
-
Christopher Dembia authored
The pragma to ignore 4251 already existed in windowsIncludes.h, and it works when compiling lepton itself. However, when clients use lepton, they get this warning. I think this is why @sherm1 put the define as shown here: https://github.com/simbody/simbody/blob/master/SimTKcommon/include/SimTKcommon/internal/common.h#L168 (whether or not the shared library is being built or used).
-
- 18 Sep, 2014 1 commit
-
-
peastman authored
-
- 16 Sep, 2014 4 commits
- 10 Jul, 2014 2 commits
-
-
Christopher Dembia authored
-
Christopher Dembia authored
-
- 16 Jun, 2014 1 commit
-
-
Christopher Dembia authored
Clang had been generating the following warning: ``` ParsedExpression.cpp:123:13: warning: 30 enumeration values not handled in switch: 'CONSTANT', 'VARIABLE', 'CUSTOM'... [-Wswitch] switch (node.getOperation().getId()) { ^ 1 warning generated. ``` To get rid of this warning, I added a default case, which does nothing.
-
- 12 Dec, 2013 1 commit
-
-
peastman authored
-
- 17 Oct, 2013 1 commit
-
-
peastman authored
-
- 16 Oct, 2013 1 commit
-
-
peastman authored
-
- 03 Jul, 2013 1 commit
-
-
peastman authored
-
- 07 May, 2012 1 commit
-
-
Peter Eastman authored
-
- 18 Oct, 2011 1 commit
-
-
Peter Eastman authored
-
- 17 Oct, 2011 1 commit
-
-
Peter Eastman authored
-
- 19 Sep, 2011 1 commit
-
-
Peter Eastman authored
-
- 12 Aug, 2010 1 commit
-
-
Peter Eastman authored
-
- 19 Apr, 2010 1 commit
-
-
Christopher Bruns authored
-
- 16 Apr, 2010 1 commit
-
-
Peter Eastman authored
-
- 05 Jan, 2010 1 commit
-
-
Peter Eastman authored
-
- 10 Dec, 2009 1 commit
-
-
Peter Eastman authored
-
- 05 Dec, 2009 1 commit
-
-
Peter Eastman authored
-
- 24 Nov, 2009 1 commit
-
-
Peter Eastman authored
-
- 23 Nov, 2009 1 commit
-
-
Peter Eastman authored
-