https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124422
--- Comment #5 from Roland Illig <roland.illig at gmx dot de> --- (In reply to Andrew Pinski from comment #1) > > "that exceeds 16 bytes" -> > > "that exceeds 16 bits" > > (2 times) > > Without context this might be still bytes. The context in this case is the code, which says "1 << 15", both positive and negative, which amounts to 16 bits of address space. > > "types may not be defined" -> "types must not be defined" > > (in 22 messages) > > I am not sure that makes a difference. Both are correct and have slightly > different meanings. Without the context `may not be` may be correct. >From when I have learnt English, "may not" means "it is possibly false" while "must not" means "it has to be definitely false". "new types may not be defined" could thus mean that "in this case, it could happen that the new type is not defined, so the new type is effectively ignored". This misunderstanding is what I wanted to avoid. I quoted exactly the part "types may not be defined" to limit the discussion to cp/parser.cc.
