public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: h.b.furuseth@usit.uio.no
To: gcc-gnats@gcc.gnu.org
Cc: h.b.furuseth@usit.uio.no
Subject: c/3347: Too large bitfields should be errors
Date: Thu, 21 Jun 2001 13:06:00 -0000	[thread overview]
Message-ID: <E15DAct-0000Nu-00@bombur.uio.no> (raw)

>Number:         3347
>Category:       c
>Synopsis:       Too large bitfields should be errors
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Thu Jun 21 13:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Hallvard B Furuseth
>Release:        3.0 20010611 (prerelease)
>Organization:
University of Oslo, Norway
>Environment:
System: SunOS bombur.uio.no 5.8 Generic_108528-03 sun4u sparc SUNW,Ultra-5_10
Architecture: sun4

	
host: sparc-sun-solaris2.8
build: sparc-sun-solaris2.8
target: sparc-sun-solaris2.8
configured with: ./configure --quiet
>Description:
	A too large bitfield is a constraint violation of C99 6.7.2.1p3.
	I think it violates ANSI and K&R too, but I can't check that.
	Gcc only gives a plain warning, even under -std=c99 -pedantic.
>How-To-Repeat:
	bash$ echo 'struct { int i : 9999; } x;' > a.c
	bash$ ./xgcc -B./ -std=c99 -pedantic -o /dev/null -S a.c

	a.c:1: warning: width of `i' exceeds its type
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-06-21 13:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 13:06 h.b.furuseth [this message]
2002-01-29  9:22 neil
2002-02-01 20:55 neil

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=E15DAct-0000Nu-00@bombur.uio.no \
    --to=h.b.furuseth@usit.uio.no \
    --cc=gcc-gnats@gcc.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.
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).