Opened 12 years ago
Closed 11 years ago
#4315 closed Patches (fixed)
gcc 4.4 Warning: inline ... declared as dllimport: attribute ignored
Reported by: | viboes | Owned by: | viboes |
---|---|---|---|
Milestone: | Boost 1.49.0 | Component: | thread |
Version: | Boost Development Trunk | Severity: | Cosmetic |
Keywords: | Cc: | feiyunw@…, viboes |
Description
The following warnings appears on gcc4.4 mingw:
gcc.compile.c++ ..\..\..\bin.v2\libs\thread\test\test_thread_id.test\gcc-mingw-4.4.0\debug\threading-multi\test_thread_id.o In file included from ..\..\../boost/thread/win32/thread_data.hpp:12,
from ..\..\../boost/thread/thread.hpp:15, from test_thread_id.cpp:5:
..\..\../boost/thread/win32/thread_heap_alloc.hpp:59: warning: inline function 'void* boost::detail::allocate_raw_heap_memory(unsigned int)' declared as dllimport: attribute ignored ..\..\../boost/thread/win32/thread_heap_alloc.hpp:69: warning: inline function 'void boost::detail::free_raw_heap_memory(void*)' declared as dllimport: attribute ignored
Can a inline function be declared as dllimport?
Attachments (1)
Change History (7)
by , 12 years ago
Attachment: | 4315.patch added |
---|
comment:1 by , 12 years ago
Type: | Support Requests → Patches |
---|
follow-up: 3 comment:2 by , 11 years ago
Cc: | added |
---|---|
Milestone: | Boost 1.43.0 → Boost 1.48.0 |
Version: | Boost 1.44.0 → Boost Development Trunk |
comment:3 by , 11 years ago
Replying to feiyunw@…:
I am sorry that this one is not solved for more than one year.
Hi I'm new to boost and am writing a basic asio app as a learning exercise. Should I be worried about these warnings? do they represent genuine issues?
comment:4 by , 11 years ago
Cc: | added |
---|---|
Milestone: | Boost 1.48.0 → Boost 1.49.0 |
Owner: | changed from | to
Status: | new → assigned |
Committed in trunk at revision: 75791
comment:6 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Committed in release at #76291
Component thread is one of the two boost components which generates warnings when compiled in MinGW/MSYS with gcc-4.5.2:
The preceding numbers are the numbers of occurrence.
I am sorry that this one is not solved for more than one year.