--- Comment #7 from mckelvey at maskull dot com 2008-02-19 00:58 ---
How can GCC conclude that a call is going to be infrequent? Doesn't that
amount to predicting the future? Also, if an object is constructed, then it
will
be destroyed. So there is almost a 100% chance of calling the des
--- Comment #6 from hubicka at gcc dot gnu dot org 2008-02-17 19:45 ---
OK, I am switching it to new again ;)
However the warning really means that GCC decided to not inline the function
because it thinks it is not profitable because it concluded that the call is
infrequent. Perhaps you
--- Comment #5 from James dot W dot Mckelvey at jpl dot nasa dot gov
2007-07-13 15:28 ---
(In reply to comment #3)
> Can you attach the preprocessed source?
>
I did on June 10, I see the status is still Waiting.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32089
--- Comment #4 from mckelvey at maskull dot com 2007-06-10 22:52 ---
Created an attachment (id=13674)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13674&action=view)
Preprocessed source
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32089
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-06-10 03:24 ---
Can you attach the preprocessed source?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #2 from mckelvey at maskull dot com 2007-05-25 23:03 ---
Here is how I compile it:
/usr/local/bin/g++ -c -O3 -DNDEBUG -Wuninitialized -pedantic-errors -Werror
-Winline -ansi -fno-common -Wall -Wold-style-cast -Wsign-promo -Wpointer-arith
-Wundef -Wwrite-strings -Winvalid-p
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-25 22:30 ---
First the deconstructor was either defaulted to inline or marked as such.
Second what are the full options do you use?
If the call is unlikely (which it says in your case), then there is no reason
to inline it. I b
