Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support LLVM trunk #3907

Merged
merged 3 commits into from
Sep 7, 2019
Merged

Support LLVM trunk #3907

merged 3 commits into from
Sep 7, 2019

Conversation

yzhliu
Copy link
Member

@yzhliu yzhliu commented Sep 6, 2019

LLVM trunk (10.0) requires c++14
(I don't find the exact "announcement", but here is a related one, https://lists.llvm.org/pipermail/llvm-dev/2018-October/127045.html )

@zhiics @icemelon9 @jroesch @tqchen Please review.

@yzhliu yzhliu changed the title support LLVM trunk Support LLVM trunk Sep 6, 2019
@icemelon
Copy link
Member

icemelon commented Sep 6, 2019

Should we use c++14 by default when available?

@MarisaKirisame
Copy link
Contributor

personally I dont see why not. python2 is deprecated and C++14 is out 5 years ago. giving how fast deep learning is moving I see no incentive to restrict ourselves to 11.

@zhiics
Copy link
Member

zhiics commented Sep 6, 2019

I think C++14 is the default since clang-6.0. But will our submodules cause problem?

@yzhliu
Copy link
Member Author

yzhliu commented Sep 6, 2019

One concern is that, MXNet is using c++11, and for the recently merged feature (use tvm to write mxnet op), we need to compile TVM in MXNet, it will cause problem.

@yzhliu
Copy link
Member Author

yzhliu commented Sep 6, 2019

And some internal systems are still using gcc 4.8/4.9 as I know.

if ("${CMAKE_BUILD_TYPE}" STREQUAL "Debug")
message("Build in Debug mode")
set(CMAKE_C_FLAGS "-O0 -g -Wall -fPIC ${CMAKE_C_FLAGS} -rdynamic")
set(CMAKE_CXX_FLAGS "-O0 -g -Wall -fPIC -std=c++11 ${CMAKE_CXX_FLAGS} -rdynamic")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we revert this then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why? I move it to the if(NOT MSVC) ... part below.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. That should be fine. Sorry about it.

@yzhliu
Copy link
Member Author

yzhliu commented Sep 7, 2019

Merge it for now as I need it for feature deliver. Thanks @MarisaKirisame @icemelon9 @zhiics I can open an RFC to discuss the timeline to move to c++14/17

@yzhliu yzhliu merged commit 8c50469 into apache:master Sep 7, 2019
MarisaKirisame pushed a commit to MarisaKirisame/tvm that referenced this pull request Sep 7, 2019
* support LLVM trunk

* guard with USE_LLVM in if condition for c++14

* GREATER_EQUAL -> GREATER
wweic pushed a commit to wweic/tvm that referenced this pull request Sep 16, 2019
* support LLVM trunk

* guard with USE_LLVM in if condition for c++14

* GREATER_EQUAL -> GREATER
wweic pushed a commit to wweic/tvm that referenced this pull request Sep 16, 2019
* support LLVM trunk

* guard with USE_LLVM in if condition for c++14

* GREATER_EQUAL -> GREATER
wweic pushed a commit to neo-ai/tvm that referenced this pull request Sep 16, 2019
* support LLVM trunk

* guard with USE_LLVM in if condition for c++14

* GREATER_EQUAL -> GREATER
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants