This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Fwd: -Wpointer-sign for GCC 4.1
- From: Daniel Jacobowitz <drow at false dot org>
- To: Jim Blandy <jimb at red-bean dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 18 Jan 2006 13:44:26 -0500
- Subject: Re: Fwd: -Wpointer-sign for GCC 4.1
- References: <20060117211914.GA13055@nevyn.them.org> <39BD9F7D-F512-40EA-804A-DBE9BAC97E2B@apple.com> <20060118173155.GM28863@synopsys.com> <8f2776cb0601181040s4970ce9es15ebdcae50dccda2@mail.gmail.com>
On Wed, Jan 18, 2006 at 10:40:55AM -0800, Jim Blandy wrote:
> The message below is kind of odd. We do use -Wall
No, we don't. See the comments in configure.ac about this.
>, so if the pointer
> sign warning will be printed when -Wall is specified, we'll still need
> to pass an explicit argument to disable it. Which doesn't exactly
> take the decision out of our hands, as we were hoping.
>
> I think we should decide, for ourselves, whether we think the warning
> is helpful or not, and then not be demure about doing the necessary
> GCC stuff to enable or disable it. Hoping GCC would answer the
> question for us was dopey.
Sorry, that wasn't my goal. My goal with forwarding this to the GCC
list was independent of what GDB should do - as Joe wrote, the GCC SC
made a promise to RMS that I'm trying to make sure doesn't slip through
the cracks.
> I think there's some documentation value in reserving gdb_byte for
> binary blobs and char for host-format text. It wouldn't have been
> worth it before, but at this point we've got fixes for almost all
> those warnings in place; we can't get those hours back, so the
> cost/benefit is different now. So I think we should continue to
> request the warning.
Almost all of those warnings on some targets, btw. An ARM cross
debugger has a whole new set of them. I don't know which option I
prefer. Either way I'll probably clean up ARM soonish.
--
Daniel Jacobowitz
CodeSourcery