[Bug target/50779] always_inline function fails to inline

2024-10-24 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50779 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug target/50779] always_inline function fails to inline

2011-10-19 Thread vanboxem.ruben at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50779 --- Comment #5 from Ruben Van Boxem 2011-10-19 10:37:37 UTC --- There's this on msdn about inline and dllexport: http://msdn.microsoft.com/en-us/library/xa0d9ste.aspx On top of this, MSVC allows its __forceinline to be used in a dllexport contex

[Bug target/50779] always_inline function fails to inline

2011-10-19 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50779 --- Comment #4 from Richard Guenther 2011-10-19 10:23:37 UTC --- So it's probably similar to ELF platforms using a weak always-inline function. Thus a conflict in marking it replacable at link-time and inlinable. If dllexport does not have this s

[Bug target/50779] always_inline function fails to inline

2011-10-19 Thread vanboxem.ruben at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50779 --- Comment #3 from Ruben Van Boxem 2011-10-19 10:17:54 UTC --- Sorry about that: m:\Development\source\qtcreator\src\shared\proparser\profileparser.cpp: In member function 'void ProFileParser::leaveScope(ushort*&)': m:\Development\source\qtcrea

[Bug target/50779] always_inline function fails to inline

2011-10-19 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50779 Richard Guenther changed: What|Removed |Added Keywords||rejects-valid Status|UNCON

[Bug target/50779] always_inline function fails to inline

2011-10-18 Thread vanboxem.ruben at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50779 --- Comment #1 from Ruben Van Boxem 2011-10-18 18:43:39 UTC --- Created attachment 25547 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=25547 Compile with "g++ -O[012] -c profileparser.ii" to trigger the error (preprocessed with x86_64-w64-m