As Olaf says, a view is essentially a macro, and at compilation the view text is replaced with the view definition. Optimization is then performed on the expanded query, and the view as such may not be computed.
However, when a view appears multiple times in a query, this typically leads to extra processing, as SQL Server does not have a way to find that a pattern reoccurs in a query.
The exception is if the view is an indexed view, then SQL Server may match the view against the clustered index, if you are on Enterprise Edition, or you use the NOEXPAND hint.
So short summary: having the same view reappearing in the query may not be good for performance, although the exact consequence depends on the specific case.