mxnet
                                
                                
                                
                                    mxnet copied to clipboard
                            
                            
                            
                        Set -fstandalone-debug in clang debug builds
"Clang supports a number of optimizations to reduce the size of debug information in the binary. They work based on the assumption that the debug type information can be spread out over multiple compilation units. For instance, Clang will not emit type definitions for types that are not needed by a module and could be replaced with a forward declaration. Further, Clang will only emit type info for a dynamic C++ class in the module that contains the vtable for the class.
The -fstandalone-debug option turns off these optimizations. This is useful when working with 3rd-party libraries that don’t come with debug information. Note that Clang will never emit type information for types that are not referenced at all by the program."
Without -fstandalone-debug, lldb usage is degraded as debug information of C++ standard library types such strings or containers will be unusable and the types cannot be printed in lldb. Thus set the option by default in clang builds to assist developers unfamiliar with clang / lldb intricacies.
Hey @leezu , Thanks for submitting the PR All tests are already queued to run once. If tests fail, you can trigger one or more tests again with the following commands:
- To trigger all jobs: @mxnet-bot run ci [all]
 - To trigger specific jobs: @mxnet-bot run ci [job1, job2]
 
CI supported jobs: [windows-cpu, sanity, miscellaneous, centos-cpu, website, edge, windows-gpu, unix-gpu, centos-gpu, clang, unix-cpu]
Note: Only following 3 categories can trigger CI :PR Author, MXNet Committer, Jenkins Admin. All CI tests must pass before the PR can be merged.
@mxnet-bot run ci [centos-gpu, miscellaneous]
Jenkins CI successfully triggered : [centos-gpu, miscellaneous]