This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug optimization/11680] member access of C++ class with all methods inline should be optimized better
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Jul 2003 09:34:12 -0000
- Subject: [Bug optimization/11680] member access of C++ class with all methods inline should be optimized better
- References: <20030727051349.11680.dbaron@dbaron.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11680
------- Additional Comments From gdr at integrable-solutions dot net 2003-07-27 09:34 -------
Subject: Re: New: member access of C++ class with all methods inline should be optimized better
"dbaron at dbaron dot org" <gcc-bugzilla@gcc.gnu.org> writes:
| In particular, the code involved a large inline method that involved repeated
| use of a member variable (being used as a cursor into the output buffer being
| written). (By default, gcc didn't inline the method. This was hand-optimized
| by using |__attribute__((always_inline))|. Should I file a separate bug on
| this, or is it unlikely to be fixed?)
Please fill a bug report. GCC should implement the obvious and original
meaning of "inline". That it failed is a bug.
That one should ressort to contorsions and unspeakable syntax like
__attribute__((always_inline)) while we have the obivous syntax is
also a bug.
-- Gaby