From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gpion@lfdj.com, 13408@debbugs.gnu.org
Subject: bug#13408: Emacs pretest 24.2.92 - compilation error on AIX 5.3 using gcc 4.7-2
Date: Fri, 11 Jan 2013 11:11:25 -0800 [thread overview]
Message-ID: <50F063DD.2040504@cs.ucla.edu> (raw)
In-Reply-To: <83hamoulkj.fsf@gnu.org>
On 01/11/2013 01:15 AM, Eli Zaretskii wrote:
>> Date: Fri, 11 Jan 2013 00:03:39 -0800
>> > From: Paul Eggert <eggert@cs.ucla.edu>
>> >
>> > The other problem is due to a stray '*'. This was fixed a while ago
>> > in the trunk, so I backported that to emacs-24 as bzr 111171.
> Do you happen to know what did GCC make out that, before the change?
> Did it just ignore the dereference?
No, GCC consistently refused to compile it. It's just that
this code is rarely compiled -- it's normally ifdeffed out,
so GCC doesn't see the problem. I suppose that on AIX the
code is not ifdeffed out, so that's why the bug was reported
for AIX.
In older Emacs versions, the types were different and the
"*" was OK; it became a stray "*" only fairly recently.
next prev parent reply other threads:[~2013-01-11 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 17:46 bug#13408: Emacs pretest 24.2.92 - compilation error on AIX 5.3 using gcc 4.7-2 Gilles Pion
2013-01-11 6:26 ` Glenn Morris
2013-01-11 8:24 ` Eli Zaretskii
2013-01-11 8:03 ` Paul Eggert
2013-01-11 9:15 ` Eli Zaretskii
2013-01-11 19:11 ` Paul Eggert [this message]
2013-01-11 19:51 ` conservative stack scanning (was: Re: bug#13408: Emacs pretest 24.2.92 - compilation error on AIX 5.3 using gcc 4.7-2) Stefan Monnier
2013-01-12 1:51 ` conservative stack scanning Paul Eggert
2013-01-12 2:15 ` Broken !GC_MARK_STACK [Re: conservative stack scanning] Dmitry Antipov
2013-01-12 6:19 ` Paul Eggert
2013-01-14 9:59 ` Dmitry Antipov
2013-01-12 4:23 ` conservative stack scanning Stefan Monnier
2013-01-12 5:22 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50F063DD.2040504@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=13408@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gpion@lfdj.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.