Not really "goto statements" so much as the go-to arbitrary control flow semantic aka jump.
C's goto is a housecat to the full blown jump's tiger. No doubt an angry housecat is a nuisance but the tiger is much more dangerous.
C goto won't let you jump straight into the middle of unrelated code, for example, but the jump instruction has no such limit and neither did the feature Dijkstra was discussing.
https://en.wikipedia.org/wiki/Considered_harmful