unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* differ in signdness warnings.
@ 2005-12-02 15:03 Jan D.
  2005-12-02 17:32 ` Romain Francoise
  2005-12-02 18:40 ` Eli Zaretskii
  0 siblings, 2 replies; 9+ messages in thread
From: Jan D. @ 2005-12-02 15:03 UTC (permalink / raw)


Hello.

With gcc >= 4.0 I get a lot of these when compiling Emacs:

coding.c:3471: varning: pointer targets in passing argument 1 of 
"safe_bcopy" differ in signedness

coding.c:3471: varning: pointer targets in passing argument 2 of 
"safe_bcopy" differ in signedness

frame.c:2107: varning: pointer targets in passing argument 1 of 
"strncmp" differ in signedness

and so on.

Is there anything said about what to do about these?  Should we ignore 
them or add casts where appropriate?  Introducing a SSDATA, which is 
(char *)SDATA, would be a good idea.

    Jan D.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-02 15:03 differ in signdness warnings Jan D.
@ 2005-12-02 17:32 ` Romain Francoise
  2005-12-03  1:20   ` Richard M. Stallman
  2005-12-02 18:40 ` Eli Zaretskii
  1 sibling, 1 reply; 9+ messages in thread
From: Romain Francoise @ 2005-12-02 17:32 UTC (permalink / raw)


"Jan D." <jan.h.d@swipnet.se> writes:

> Is there anything said about what to do about these?  Should we ignore
> them or add casts where appropriate?

I just compile with -Wno-pointer-sign.

-- 
Romain Francoise <romain@orebokech.com> | The sea! the sea! the open
it's a miracle -- http://orebokech.com/ | sea! The blue, the fresh, the
                                        | ever free! --Bryan W. Procter

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-02 15:03 differ in signdness warnings Jan D.
  2005-12-02 17:32 ` Romain Francoise
@ 2005-12-02 18:40 ` Eli Zaretskii
  2005-12-03 14:21   ` Jan Djärv
  2005-12-03 15:58   ` Richard M. Stallman
  1 sibling, 2 replies; 9+ messages in thread
From: Eli Zaretskii @ 2005-12-02 18:40 UTC (permalink / raw)
  Cc: emacs-devel

> Date: Fri, 02 Dec 2005 16:03:40 +0100
> From: "Jan D." <jan.h.d@swipnet.se>
> 
> With gcc >= 4.0 I get a lot of these when compiling Emacs:
> 
> coding.c:3471: varning: pointer targets in passing argument 1 of 
> "safe_bcopy" differ in signedness
> 
> coding.c:3471: varning: pointer targets in passing argument 2 of 
> "safe_bcopy" differ in signedness
> 
> frame.c:2107: varning: pointer targets in passing argument 1 of 
> "strncmp" differ in signedness
> 
> and so on.
> 
> Is there anything said about what to do about these?

How about if we complain loudly to the GCC maintainers about these
silly warnings, and ask them to modify GCC so that it issues them only
under -Wall?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-02 17:32 ` Romain Francoise
@ 2005-12-03  1:20   ` Richard M. Stallman
  2005-12-03  9:25     ` Eli Zaretskii
  0 siblings, 1 reply; 9+ messages in thread
From: Richard M. Stallman @ 2005-12-03  1:20 UTC (permalink / raw)
  Cc: emacs-devel

    I just compile with -Wno-pointer-sign.

How about making this the default?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-03  1:20   ` Richard M. Stallman
@ 2005-12-03  9:25     ` Eli Zaretskii
  2005-12-04  3:08       ` Richard M. Stallman
  0 siblings, 1 reply; 9+ messages in thread
From: Eli Zaretskii @ 2005-12-03  9:25 UTC (permalink / raw)
  Cc: romain, emacs-devel

> From: "Richard M. Stallman" <rms@gnu.org>
> Date: Fri, 02 Dec 2005 20:20:38 -0500
> Cc: emacs-devel@gnu.org
> 
>     I just compile with -Wno-pointer-sign.
> 
> How about making this the default?

That would add complexity that we should try to avoid: we will need to
add tests to the configury that probe whether GCC used for the build
supports this option.

I really think we should try to convince GCC maintainers to make
"-Wno-pointer-sign" be the default.  Then we need do nothing in Emacs.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-02 18:40 ` Eli Zaretskii
@ 2005-12-03 14:21   ` Jan Djärv
  2005-12-03 15:58   ` Richard M. Stallman
  1 sibling, 0 replies; 9+ messages in thread
From: Jan Djärv @ 2005-12-03 14:21 UTC (permalink / raw)
  Cc: emacs-devel

Eli Zaretskii wrote:
>>Date: Fri, 02 Dec 2005 16:03:40 +0100
>>From: "Jan D." <jan.h.d@swipnet.se>
>>
>>With gcc >= 4.0 I get a lot of these when compiling Emacs:
>>
>>coding.c:3471: varning: pointer targets in passing argument 1 of 
>>"safe_bcopy" differ in signedness
>>
>>coding.c:3471: varning: pointer targets in passing argument 2 of 
>>"safe_bcopy" differ in signedness
>>
>>frame.c:2107: varning: pointer targets in passing argument 1 of 
>>"strncmp" differ in signedness
>>
>>and so on.
>>
>>Is there anything said about what to do about these?
> 
> 
> How about if we complain loudly to the GCC maintainers about these
> silly warnings, and ask them to modify GCC so that it issues them only
> under -Wall?

I am all for that!

	Jan D.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-02 18:40 ` Eli Zaretskii
  2005-12-03 14:21   ` Jan Djärv
@ 2005-12-03 15:58   ` Richard M. Stallman
  2005-12-03 16:07     ` Eli Zaretskii
  1 sibling, 1 reply; 9+ messages in thread
From: Richard M. Stallman @ 2005-12-03 15:58 UTC (permalink / raw)
  Cc: jan.h.d, emacs-devel

    How about if we complain loudly to the GCC maintainers about these
    silly warnings, and ask them to modify GCC so that it issues them only
    under -Wall?

I would support asking them to show a justification for this change.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-03 15:58   ` Richard M. Stallman
@ 2005-12-03 16:07     ` Eli Zaretskii
  0 siblings, 0 replies; 9+ messages in thread
From: Eli Zaretskii @ 2005-12-03 16:07 UTC (permalink / raw)
  Cc: emacs-devel

> From: "Richard M. Stallman" <rms@gnu.org>
> CC: jan.h.d@swipnet.se, emacs-devel@gnu.org
> Date: Sat, 03 Dec 2005 10:58:30 -0500
> 
>     How about if we complain loudly to the GCC maintainers about these
>     silly warnings, and ask them to modify GCC so that it issues them only
>     under -Wall?
> 
> I would support asking them to show a justification for this change.

Could you perhaps actually write to them?  Based on my past (and
bitter) experience of talking to them about similar issues, it will
probably take your authority to get them to give any serious and
technical answers.

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: differ in signdness warnings.
  2005-12-03  9:25     ` Eli Zaretskii
@ 2005-12-04  3:08       ` Richard M. Stallman
  0 siblings, 0 replies; 9+ messages in thread
From: Richard M. Stallman @ 2005-12-04  3:08 UTC (permalink / raw)
  Cc: romain, emacs-devel

    That would add complexity that we should try to avoid: we will need to
    add tests to the configury that probe whether GCC used for the build
    supports this option.

That should not be hard using autoconf.

    I really think we should try to convince GCC maintainers to make
    "-Wno-pointer-sign" be the default.  Then we need do nothing in Emacs.

I will start by asking them what their reason was.

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2005-12-04  3:08 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-12-02 15:03 differ in signdness warnings Jan D.
2005-12-02 17:32 ` Romain Francoise
2005-12-03  1:20   ` Richard M. Stallman
2005-12-03  9:25     ` Eli Zaretskii
2005-12-04  3:08       ` Richard M. Stallman
2005-12-02 18:40 ` Eli Zaretskii
2005-12-03 14:21   ` Jan Djärv
2005-12-03 15:58   ` Richard M. Stallman
2005-12-03 16:07     ` Eli Zaretskii

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).