[llvm-bugs] [Bug 35014] New: Need a way to disable "warning: symbol scopes are not balanced in" for system libraries

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Oct 20 13:05:55 PDT 2017


https://bugs.llvm.org/show_bug.cgi?id=35014

            Bug ID: 35014
           Summary: Need a way to disable "warning: symbol scopes are not
                    balanced in" for system libraries
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: COFF
          Assignee: unassignedbugs at nondot.org
          Reporter: nicolasweber at gmx.de
                CC: llvm-bugs at lists.llvm.org

If I build chromium with lld, virtually every link prints this:

[15895/50568] LINK(DLL) swiftshader/libGLESv2.dll swiftshader/libGLESv2.dll.lib
swiftshader/libGLESv2.dll.pdb
../../third_party/llvm-build/Release+Asserts/bin/lld-link: warning: symbol
scopes are not balanced in
f:\binaries\Intermediate\vctools\libconcrt.nativeproj__2086454777\objr\x86\InternalContextBase.obj
../../third_party/llvm-build/Release+Asserts/bin/lld-link: warning: symbol
scopes are not balanced in
f:\binaries\Intermediate\vctools\libconcrt.nativeproj__2086454777\objr\x86\InternalContextBase.obj
../../third_party/llvm-build/Release+Asserts/bin/lld-link: warning: symbol
scopes are not balanced in
f:\binaries\Intermediate\vctools\libconcrt.nativeproj__2086454777\objr\x86\ThreadScheduler.obj
../../third_party/llvm-build/Release+Asserts/bin/lld-link: warning: symbol
scopes are not balanced in
f:\binaries\Intermediate\vctools\libconcrt.nativeproj__2086454777\objr\x86\ThreadScheduler.obj
../../third_party/llvm-build/Release+Asserts/bin/lld-link: warning: symbol
scopes are not balanced in
f:\binaries\Intermediate\vctools\libconcrt.nativeproj__2086454777\objr\x86\ThreadScheduler.obj


This is not interesting and actionable for application developers (...unless
some flag we uses causes this?). So it shouldn't be printed.

Also, it'd be good if there was a way to consistently enable warnings-as-errors
for lld. In Chromium, our philosophy about warnings is in general "if it's an
interesting warning, it deserves to be made an error, else it shouldn't be
printed at all".

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171020/51420cd4/attachment.html>


More information about the llvm-bugs mailing list