Testing Unit's Efficiency in TDD

Let's say we need a sort function and want to ensure that it is implemented in O(nlogn) rather than O(n^2).

Using test driven development, is there a systematic way to test the efficiency of implementation of this function?

According to Wikipedia, Testing implementation details is considered an anti-pattern in Test Driven Development, does this prevent TDD from any attempt to check the efficiency of the code satisfying a requirement? Or is there a systematic way for doing so?