Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-27 Thread Anaya Shah via Gcc
Hello, I apologise for this problem, but I've been recieving emails regarding the project you are working on. However, I'm unable to understand the context of this project. But it looks exciting! I would be thankful if you can help me through the project framework, and share the exact details, so

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Florian Weimer via Gcc
* Arsen Arsenović via Gcc: > Sam James via Gcc writes: > >> Florian Weimer via Gcc writes: >> >>> My understanding of the consensus goes as follows: >>> >>> * We want to make some changes in this area for GCC 14. >>> * We should do the same thing that Clang does: default to the relevant >>> -W

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Arsen Arsenović via Gcc
Sam James via Gcc writes: > Florian Weimer via Gcc writes: > >> My understanding of the consensus goes as follows: >> >> * We want to make some changes in this area for GCC 14. >> * We should do the same thing that Clang does: default to the relevant >> -Werror= options. >> * Unlike regular w

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Sam James via Gcc
Jeff Law via Gcc writes: > On 9/26/23 02:28, Florian Weimer via Gcc wrote: >> My understanding of the consensus goes as follows: >> * We want to make some changes in this area for GCC 14. >> * We should do the same thing that Clang does: default to the relevant >>-Werror= options. >> * Unli

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Sam James via Gcc
Florian Weimer via Gcc writes: > My understanding of the consensus goes as follows: > > * We want to make some changes in this area for GCC 14. > * We should do the same thing that Clang does: default to the relevant > -Werror= options. > * Unlike regular warnings, these warnings-as-errors sh

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Florian Weimer via Gcc
* Jeff Law: >> I think the open issues are: >> * Do we want to implement something else beside implicit-int and >>implicit-function-declaration? (Candidates are int-conversion and >>incompatible-pointer-types, and the void vs non-void part of >>return-type, maybe others as previously

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Jeff Law via Gcc
On 9/26/23 02:28, Florian Weimer via Gcc wrote: My understanding of the consensus goes as follows: * We want to make some changes in this area for GCC 14. * We should do the same thing that Clang does: default to the relevant -Werror= options. * Unlike regular warnings, these warnings-as-e

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Florian Weimer via Gcc
* Jakub Jelinek: > On Tue, Sep 26, 2023 at 10:28:34AM +0200, Florian Weimer via Gcc wrote: >> My understanding of the consensus goes as follows: >> >> * We want to make some changes in this area for GCC 14. >> * We should do the same thing that Clang does: default to the relevant >> -Werror= op

Re: Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Jakub Jelinek via Gcc
On Tue, Sep 26, 2023 at 10:28:34AM +0200, Florian Weimer via Gcc wrote: > My understanding of the consensus goes as follows: > > * We want to make some changes in this area for GCC 14. > * We should do the same thing that Clang does: default to the relevant > -Werror= options. I think it doesn'

Report from the additional type errors for GCC 14 BoF at Cauldron

2023-09-26 Thread Florian Weimer via Gcc
My understanding of the consensus goes as follows: * We want to make some changes in this area for GCC 14. * We should do the same thing that Clang does: default to the relevant -Werror= options. * Unlike regular warnings, these warnings-as-errors should also apply to system headers. * At leas