Re: Discussion about why GNU/Linux system upgrades cause old programs to break
Richard Stallman <[email protected]>
| Newsgroups | gmane.emacs.devel |
|---|---|
| Message-ID | <[email protected]> |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> GCC 14 considers certain K&R C constructs an error in C99 mode and
> newer, whereas GCC up to 13 merely warned for them in those same modes.
> See https://gcc.gnu.org/gcc-14/porting_to.html#warnings-as-errors
> including on details how to recover old behavior.
I looked at that page, and found many instances of old practices
that now cause errors. These are some examples.
Implicit int types (-Werror=implicit-int)
Type checking on pointer types (-Werror=incompatible-pointer-types)
Implicit function declarations (-Werror=implicit-function-declaration)
What arguments can restore GCC 13 behavior for these cases, and the
other cases described there?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)