What version of Go are you using (go version)?

$ go version
go version devel +3d48ae3 Wed Aug 28 03:23:59 2019 +0000 linux/amd64

Does this issue reproduce with the latest release?

Yes.

What did you do?

I played around with some switch statements over strings to check how the gc would behave.
For example, the switch in the following function has some issues (https://godbolt.org/z/L-Z-TM):

func f(x string) int {
	switch x {
	case "":
		return -1
	case "1", "2", "3":
		return -2
	default:
		return -3
	}
}

What did you expect to see?

I expected the generated assembly code to be relatively simple, with no redundant instructions or jumps.

What did you see instead?

Instead, I can see some redundancies in the output of the compiler (below, I will be referring to the lines in the website mentioned above):

1. In line 79, the comparison x == "1" uses runtime.cmpstring, while the others compare x directly with an int
2. In line 18, its checked if len(x) == 0, which is never true, give that the check on line 16 has failed
3. In line 81, the jump should be to the return -3 block
4. If I follow some paths of execution, there are a lot of double jumps (jeq -> jeq and jeq -> jne)