1.27.0 Compiler Options: no-redzone option (Is the explanation backwards?)

[gbutler69]

In the 1.27.0 release of the "Rustc Book", the command-line option "no-redzone" is described as follows:

no-redzone

This flag allows you to disable the red zone. This flag can be passed many options:

To enable the red zone: y, yes or on.

To disable it: n, no, or off.

This sounds backwards. Should it be "no-redzone=yes" would disable the RedZone and "no-redzone=no" would enable the "RedZone"? If not, it seems like the command-line option is misnamed and should be "redzone" rather than "no-redzone".

[steveklabnik]

And related, the target spec uses disable-redzone https://github.com/intermezzOS/kernel/blob/master/intermezzos.json#L12

[Manishearth]

I think we should name it redzone=yes/no anyway, a negative flag makes sense if it's a simple boolean with no arguments whose existence always means "no", but this is a flag to which you pass a yes/no, so it should either be -Cno-redzone, or -Credzone=no/-Credzone=yes.

[roblabla]

I personally believe a -Cno-redzone boolean flag would be the best way to go, as it clearly indicates that the default is that the redzone is present.

[hkBst]

This flag allows you to disable the red zone. It takes one of the following values:

y, yes, on, true or no value: disable the red zone.
n, no, off or false: enable the red zone.

The default behaviour, if the flag is not specified, depends on the target.

So it seems this was fixed and can be closed.