Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-11 Thread Gabriel Dos Reis
Joe Buck <[EMAIL PROTECTED]> writes: | On Thu, Jan 11, 2007 at 04:09:16AM +0100, Gabriel Dos Reis wrote: | > The subtlety I'm refering to is not that "void* p = &p" is not well-defined, | > but rather the fact that when we see | > | > T t = some-expression-involving-t; | > | > we would like

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Joe Buck
On Thu, Jan 11, 2007 at 04:09:16AM +0100, Gabriel Dos Reis wrote: > The subtlety I'm refering to is not that "void* p = &p" is not well-defined, > but rather the fact that when we see > > T t = some-expression-involving-t; > > we would like to warn for cases where there is a high probability

Re: why Winit-self (was Re: proposal to clean up @node Warning Options in invoke.texi)

2007-01-10 Thread Gabriel Dos Reis
"Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes: | On 11 Jan 2007 02:08:48 +0100, Gabriel Dos Reis | <[EMAIL PROTECTED]> wrote: | > I'm well aware of the history of "-Winit-self". The issue is more | > subtile that you would like to make it appear. You would have to study | > more carefully the

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Gabriel Dos Reis
Joe Buck <[EMAIL PROTECTED]> writes: | On Thu, Jan 11, 2007 at 02:08:48AM +0100, Gabriel Dos Reis wrote: | > I'm well aware of the history of "-Winit-self". The issue is more | > subtile that you would like to make it appear. You would have to study | > more carefully the threads relating to this

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Joe Buck
On Thu, Jan 11, 2007 at 02:08:48AM +0100, Gabriel Dos Reis wrote: > I'm well aware of the history of "-Winit-self". The issue is more > subtile that you would like to make it appear. You would have to study > more carefully the threads relating to this issue. If you dig the > archive, you should

why Winit-self (was Re: proposal to clean up @node Warning Options in invoke.texi)

2007-01-10 Thread Manuel López-Ibáñez
On 11 Jan 2007 02:08:48 +0100, Gabriel Dos Reis <[EMAIL PROTECTED]> wrote: I'm well aware of the history of "-Winit-self". The issue is more subtile that you would like to make it appear. You would have to study more carefully the threads relating to this issue. If you dig the archive, you shou

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Gabriel Dos Reis
"Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes: | On 10 Jan 2007 18:48:58 +0100, Gabriel Dos Reis | <[EMAIL PROTECTED]> wrote: | > | | > | It seems to me that the only reason for Winit-self to exists is that | > | people try to silence the -Wuninitialized warnings using the init-self | > | hack

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Manuel López-Ibáñez
On 10 Jan 2007 18:48:58 +0100, Gabriel Dos Reis <[EMAIL PROTECTED]> wrote: | | It seems to me that the only reason for Winit-self to exists is that | people try to silence the -Wuninitialized warnings using the init-self | hack and then other people have to work-around that hack. I don't believe

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Manuel López-Ibáñez
On 10/01/07, Chris Pickett <[EMAIL PROTECTED]> wrote: Chris Pickett wrote: > I have a question: does -Wextra now imply -Wconversion since > -Wconversion was split into -Wconversion and -Wtraditional-conversion? I mistakenly thought it was under -Wextra. So the question should be, does -Wtraditi

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Chris Pickett
Chris Pickett wrote: I have a question: does -Wextra now imply -Wconversion since -Wconversion was split into -Wconversion and -Wtraditional-conversion? I mistakenly thought it was under -Wextra. So the question should be, does -Wtraditional now imply -Wtraditional-conversion since -Wconversi

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Chris Pickett
Gerald Pfeifer wrote: 5. Fix what I have labelled as errors. That we definitely should do. I believe some things have been changed in our current development tree (to become GCC 4.3) already. It would be great could you have a look and perhaps produce a patch for one or more of these; is thi

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Manuel López-Ibáñez
On 10/01/07, Chris Pickett <[EMAIL PROTECTED]> wrote: As far as I can tell, Manuel's original response was saying that one should not list -Wno-strict-prototypes in the default section on the basis of -Wstrict-prototypes not being default. Correct.

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Gabriel Dos Reis
Chris Pickett <[EMAIL PROTECTED]> writes: | Gabriel Dos Reis wrote: | > "Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes: | > [...] | > | > I assume the -Wno-xxx that are set by default would be moved to | > the | > | > "default" section? | | My guess is that there is a misunderstanding here. mo

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Chris Pickett
Chris Pickett wrote: Gabriel Dos Reis wrote: | > I assume the -Wno-xxx that are set by default would be moved to the | > "default" section? If you meant something else in addition, can you give an example? I'm not subscribed to the list and so I missed Tom's message: http://gcc.gnu.org/ml/g

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Chris Pickett
Gabriel Dos Reis wrote: "Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes: [...] | > I assume the -Wno-xxx that are set by default would be moved to the | > "default" section? My guess is that there is a misunderstanding here. | Warnings that are not active by default are obviously disabled,

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Gabriel Dos Reis
Tom Tromey <[EMAIL PROTECTED]> writes: | > "Chris" == Chris Pickett <[EMAIL PROTECTED]> writes: | | Chris> For one reason or another, I have spent a fair amount of time | Chris> reading and getting confused by the warnings documentation. | | Chris> 3. Get rid of the -Wno-xxx option listings

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Gabriel Dos Reis
"Manuel López-Ibáñez" <[EMAIL PROTECTED]> writes: [...] | > I assume the -Wno-xxx that are set by default would be moved to the | > "default" section? | > | | No. Why? | Warnings that are not active by default are obviously disabled, | there is no need to mention them. I don't understand. Pl

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Tom Tromey
> "Chris" == Chris Pickett <[EMAIL PROTECTED]> writes: Chris> For one reason or another, I have spent a fair amount of time Chris> reading and getting confused by the warnings documentation. Chris> 3. Get rid of the -Wno-xxx option listings, since it is not always Chris> the case that -Wxxx

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Chris Pickett
Manuel López-Ibáñez wrote: On 10 Jan 2007 05:47:19 +0100, Gabriel Dos Reis <[EMAIL PROTECTED]> wrote: Chris Pickett <[EMAIL PROTECTED]> writes: I assume the -Wno-xxx that are set by default would be moved to the "default" section? No. Warnings that are not active by default are obviously disa

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-10 Thread Manuel López-Ibáñez
On 10 Jan 2007 05:47:19 +0100, Gabriel Dos Reis <[EMAIL PROTECTED]> wrote: Chris Pickett <[EMAIL PROTECTED]> writes: | 1. Create a default section, at the top, and put all options enabled | by default there. | | 2. Try to group options so that they are closer to other connected | nodes in the g

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-09 Thread Gabriel Dos Reis
Chris Pickett <[EMAIL PROTECTED]> writes: | Hi, | | For one reason or another, I have spent a fair amount of time reading | and getting confused by the warnings documentation. This applies to | the optimizations as well, but I thought I would start with the | warnings. Today I sat down and creat

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-06 Thread Chris Pickett
Gerald Pfeifer wrote: Chris, I see you have not received any response to this yet, so let me give it a try. Thanks! I unsubscribed from the list and was surprised to see this in my inbox. Please continue to CC me on replies. On Sat, 28 Oct 2006, Chris Pickett wrote: 5. Fix what I have

Re: proposal to clean up @node Warning Options in invoke.texi

2007-01-05 Thread Gerald Pfeifer
Chris, I see you have not received any response to this yet, so let me give it a try. On Sat, 28 Oct 2006, Chris Pickett wrote: 1. Create a default section, at the top, and put all options enabled by default there. This sounds like an interesting proposal. Gaby, Joseph, what do you think?

Re: proposal to clean up @node Warning Options in invoke.texi

2006-10-28 Thread Chris Pickett
Chris Pickett wrote: I have attached the graph. I am asking for one or more people to comment on its correctness, and what I consider to be errors, as indicated in comments. I did this against 4.1.1. I just looked at the trunk invoke.texi, and I see it has changed a bit, so just to be clear

proposal to clean up @node Warning Options in invoke.texi

2006-10-28 Thread Chris Pickett
Hi, For one reason or another, I have spent a fair amount of time reading and getting confused by the warnings documentation. This applies to the optimizations as well, but I thought I would start with the warnings. Today I sat down and created a dependency graph for all of the options in th