unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Building: alloc.c:766:1: error: negative width in bit-field `_gl_verify_error_if_negative'
Date: Mon, 13 Feb 2012 13:07:02 +0000	[thread overview]
Message-ID: <20120213130702.GA26954@acm.acm> (raw)
In-Reply-To: <4F382FB0.2000506@cs.ucla.edu>

Hi, Paul.

On Sun, Feb 12, 2012 at 01:31:28PM -0800, Paul Eggert wrote:
> On 02/12/2012 03:02 AM, Alan Mackenzie wrote:
> > alloc.c:766:1: error: negative width in bit-field `_gl_verify_error_if_negative'

> I am not seeing this problem (trunk bzr 107261)
> on Fedora 15 x86-64 with GCC 4.6.2.

> That diagnostic is because the following static assertion
> is failing:

>   verify (INT_MAX <= PTRDIFF_MAX);

Hmmm.  I've grepped for "negative width in bit-field" and
_gl_verify_error_if_negative and found neither.  Come to that, I haven't
found verify either.

How can the compiler transform "INT_MAX <= PTRDIFF_MAX" into a message
about bit-field widths?

Is this not, perhaps, a bug in the compiler itself?

> which suggests that your compilation environment is misconfigured
> somehow -- I don't know of any platforms where INT_MAX
> is greater than PTRDIFF_MAX.

As far as I can make out, it isn't.  INT_MAX is 2^31-1 (checked by an
#ifdef and #warning).  PTRDIFF_MAX I couldn't verify directly, but in
/usr/include/limits.h it is either 2^31-1 or 2^63-1  (I have a 64-bit
machine).

> I suggest running 'make distclean; ./autogen.sh; ./configure; make',
> or if that fails a fresh checkout.

None of that worked.  :-(

I'm going to try googling for that error message.

Thanks!

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2012-02-13 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-12 11:02 Building: alloc.c:766:1: error: negative width in bit-field `_gl_verify_error_if_negative' Alan Mackenzie
2012-02-12 21:31 ` Paul Eggert
2012-02-13 13:07   ` Alan Mackenzie [this message]
2012-02-13 16:57     ` Paul Eggert
2012-02-13 20:34       ` Alan Mackenzie
2012-02-13 20:50         ` Paul Eggert
2012-02-13 22:41           ` Alan Mackenzie

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=20120213130702.GA26954@acm.acm \
    --to=acm@muc.de \
    --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).