--- Comment #3 from msharov at hotmail dot com 2005-11-21 15:07 ---
By its very nature, demonstrating the problem requires a large example, so I am
unable to provide a sufficiently compact one to post here. You can, however,
download the project I'm having problems with from SourceForge
--- Comment #5 from msharov at hotmail dot com 2005-11-21 15:34 ---
I would disagree. If the compiler ends up creating a function call where I
expect a simple movl, that _is_ something I want to hear about as a warning. I
have some code that uses inlines in really tight loops and having
--- Comment #7 from msharov at hotmail dot com 2005-11-21 16:01 ---
(In reply to comment #6)
This is not something that should cause -Werror to refuse compilation.
Well, according to the manpage, -Werror treats _all_ warnings as fatal, no
matter what they are about. Since -Winline
--- Comment #9 from msharov at hotmail dot com 2005-11-21 16:25 ---
(In reply to comment #8)
Depends on which C++ developers and if they have really thought about all
their
uses of inline (most have not even though they say they want functions
declared
as inline to be inlined
++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: msharov at hotmail dot com
GCC build triplet: athlon-gnu-linux
GCC host triplet: athlon-gnu-linux
GCC target triplet: athlon-gnu-linux
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24947
const objects should go to .rodata
Product: gcc
Version: 4.0.2
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: msharov at hotmail dot com
GCC
: msharov at hotmail dot com
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21587
