From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Compilation warning about PNTR_ADD
Date: Wed, 23 May 2018 17:51:03 +0300 [thread overview]
Message-ID: <83tvqyctns.fsf@gnu.org> (raw)
In-Reply-To: <5aba070d-52c7-b341-2fa9-cb87989910e0@cs.ucla.edu> (message from Paul Eggert on Tue, 22 May 2018 13:08:04 -0700)
> Cc: emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Tue, 22 May 2018 13:08:04 -0700
>
> Hmm, looks like a bug in the GCC grammar for function attributes, but if
> so it's a longstanding one as it's still in GCC 8. Anyway, I installed
> the attached to work around it.
Thanks, it now compiles cleanly here.
prev parent reply other threads:[~2018-05-23 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 18:10 Compilation warning about PNTR_ADD Eli Zaretskii
2018-05-22 19:21 ` Paul Eggert
2018-05-22 19:32 ` Eli Zaretskii
2018-05-22 20:08 ` Paul Eggert
2018-05-23 14:51 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83tvqyctns.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).