[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New warnings on emacs-26 branch with gcc 8.2.0
From: |
Yuri Khan |
Subject: |
Re: New warnings on emacs-26 branch with gcc 8.2.0 |
Date: |
Sun, 19 Aug 2018 14:08:31 +0700 |
On Sun, Aug 19, 2018 at 4:26 AM Bruno Haible <address@hidden> wrote:
> Indeed, casting through (void *) or (void (*) (void)) avoids the
> warning.
I seem to remember C does not guarantee that pointers to functions
must survive casting through void*. It does for casting between
function pointer types. So casting through (void (*)(void)) is going
to be more portable.
- Re: New warnings on emacs-26 branch with gcc 8.2.0, (continued)
- Re: New warnings on emacs-26 branch with gcc 8.2.0, Paul Eggert, 2018/08/18
- Re: New warnings on emacs-26 branch with gcc 8.2.0, Bruno Haible, 2018/08/18
- Re: New warnings on emacs-26 branch with gcc 8.2.0, Eli Zaretskii, 2018/08/18
- Re: New warnings on emacs-26 branch with gcc 8.2.0, Paul Eggert, 2018/08/18
- Re: New warnings on emacs-26 branch with gcc 8.2.0, Eli Zaretskii, 2018/08/18
- Re: New warnings on emacs-26 branch with gcc 8.2.0, Paul Eggert, 2018/08/18
Re: New warnings on emacs-26 branch with gcc 8.2.0, Eli Zaretskii, 2018/08/18
Re: New warnings on emacs-26 branch with gcc 8.2.0,
Yuri Khan <=
Re: New warnings on emacs-26 branch with gcc 8.2.0, Bruno Haible, 2018/08/19
Re: New warnings on emacs-26 branch with gcc 8.2.0, Richard Stallman, 2018/08/19
Message not availableRe: New warnings on emacs-26 branch with gcc 8.2.0, Richard Stallman, 2018/08/20
Re: New warnings on emacs-26 branch with gcc 8.2.0, Paul Eggert, 2018/08/20
Re: New warnings on emacs-26 branch with gcc 8.2.0, Richard Stallman, 2018/08/22