This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: inlining inefficiencies
Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU> writes:
| Gabriel Dos Reis <gdr@codesourcery.com> writes:
|
| > Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU> writes:
| >
| > | There are some problems with inlining as shown by the code below
| > | (derived from oopack)
| > |
| > | class Complex_d {
| > | public:
| > | double re, im;
| > | Complex_d (double r, double i) : re(r), im(i) {}
| > | Complex_d () {}
| > | };
| >
| > Incidentely, I would like to mention that the compiler seems to have
| > some unexplained difficulty to optimize similar constructs with
| > double __complex__ -- that used to be mentioned in the past, and I
| > beleive the situation doesn't improve :-(
|
| If the difficulties you mention are related to aliasing, and you have
| some testcases, please send them to me.
I did some preliminary analysis here:
http://gcc.gnu.org/ml/libstdc++/2001-11/msg00038.html
I'm suspecting some aliasing issues, but I can't tell for sure.
-- Gaby