Why do you expect removing PROT_READ to provide a security gain when running open source software compiled using reproducible builds? Just the offset into an ex

Why do you expect removing PROT_READ to provide a security gain when running open source software compiled using reproducible builds? Just the offset into an executable memory mapping is enough to know the executable code to be found. Sure it's a bit annoying, but it wouldn't prevent attackers from using it as ROP gadget.