stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <>
Subject [jira] Created: (STDCXX-403) [Intel C++ 9.1/Linux] linker error on __rw_atomic_add32
Date Tue, 08 May 2007 02:00:15 GMT
[Intel C++ 9.1/Linux] linker error on __rw_atomic_add32

                 Key: STDCXX-403
             Project: C++ Standard Library
          Issue Type: Bug
          Components: 21. Strings
    Affects Versions: 4.2
         Environment: Intel C++ 9.1/Linux x86_64
            Reporter: Martin Sebor
            Priority: Blocker
             Fix For: 4.2

In shared, optimized, thread-safe builds (12{dD}) with Intel C++ 9.1 on Linux, most string
tests are failing to link with the error below:

icc -c -I$(TOPDIR)/include/ansi   -D_REENTRANT -I$(TOPDIR)/include -I$(BUILDDIR)/include -I$(TOPDIR)/tests/include
 -cxxlib-nostd -O2  -w1   $(TOPDIR)/tests/strings/21.string.access.cpp
$(TOPDIR)/tests/strings/21.string.access.cpp(308): warning #279: controlling expression is

$(TOPDIR)/tests/strings/21.string.access.cpp(258): warning #279: controlling expression is
              RW_ASSERT (!"test logic error: unknown access overload");

icc 21.string.access.o -o 21.string.access -L$(BUILDDIR)/rwtest -lrwtest -cxxlib-nostd  -lpthread
-L$(BUILDDIR)/lib  -Wl,-R$(BUILDDIR)/lib:$(BUILDDIR)/rwtest -lstd -lcxaguard -lsupc++ -lm

ld: warning: type and size of dynamic symbol `__rw_atomic_add32' are not defined
ld: dynamic variable `__rw_atomic_add32' is zero size
ld: 21.string.access.o(.gnu.linkonce.t._Z11test_accessI8UserChar10UserTraitsIS0_E9UserAllocIS0_10AllocTypesIS0_EEEvT_PT0_PT1_RK10StringFuncRK14StringTestCase[.gnu.linkonce.t._Z11test_accessI8UserChar10UserTraitsIS0_E9UserAllocIS0_10AllocTypesIS0_EEEvT_PT0_PT1_RK10StringFuncRK14StringTestCase]+0x2c2):
unresolvable R_386_PC32 relocation against symbol `__rw_atomic_add32'
ld: final link failed: Nonrepresentable section on output
gmake: *** [21.string.access] Error 1

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message