[cfe-dev] Is TreeTransform over-eager in dropping stuff?

Sebastian Redl sebastian.redl at getdesigned.at
Wed Feb 22 01:36:23 PST 2012


I've found two instances recently where TreeTransform simply skips intermediate expressions: single-argument CXXConstructExprs and ImplicitCastExprs. Not sure why this is done - could be for efficiency reasons. However, this isn't necessarily efficient; consider:

struct WithDefault { WithDefault(int i = 0); }
template <typename T>
void fn(T t) {
  new WithDefault;

Note the new expression, which is completely non-dependent. The AST for the expression in the template is
  (CXXConstructExpr WithDefault)
      (IntegerLiteral 0)

When instantiating the CXXNewExpr, the initializer is instantiated. TreeTransform looks at the CXXConstructExpr, sees that it only has one argument, and skips it, returning the instantiation of the single argument instead. This will return the CXXDefaultArgExpr unchanged (because it is non-dependent).
The CXXNewExpr instantiation now compares the old initializer (CXXConstructExpr) to the new initializer (the CXXDefaultArgExpr contained within), sees that they are different, and thus decides that it has to rebuild the CXXNewExpr.
Which is *expensive*.

I think all the places in TreeTransform that just forward to the subexpression should check if the inner expression actually changed before blindly returning it, so as to trigger fewer redundant rebuilds.

Am I right, or is there a deeper reason to the skipping?


More information about the cfe-dev mailing list