public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: DJ Delorie <dj@redhat.com>
Cc: rth@redhat.com, gcc@gcc.gnu.org, dj@redhat.com
Subject: Re: host_integerp vs [] decls
Date: Thu, 20 Sep 2001 02:04:00 -0000	[thread overview]
Message-ID: <5.1.0.14.2.20010920110259.0248f4a8@mail.lauterbach.com> (raw)
In-Reply-To: <200109200110.VAA19338@greed.delorie.com>

At 03:10 20.09.2001, DJ Delorie wrote:

> > However, please follow the directions of the comment and remove the
> > special case from pop_level_1.  Also update the documentation such
> > that "deprecated" is now "illegal".
>
>It took a while to get the right warnings for flexible vs zero-length
>arrays, and I had to adjust some of the test cases to detect the right
>warnings, but here it all is.  No regressions on x86 linux.
>
>2001-09-19  DJ Delorie  <dj@redhat.com>
>
>         * c-typeck.c (really_start_incremental_init): Discriminate
>         between zero-length arrays and flexible arrays.
>         (push_init_level): Detect zero-length arrays and handle them
>         like fixed-sized arrays.
>         * expr.c (store_constructor): Handle zero-length arrays and
>         flexible arrays correctly.
>         * doc/extend.texi: Update zero-length array notes.
>
>2001-09-19  DJ Delorie  <dj@redhat.com>
>
>         * gcc.dg/20000926-1.c: Update expected warning messages.
>         * gcc.dg/array-2.c: Likewise, and test for warnings too.
>         * gcc.dg/array-4.c: Likewise, and don't verify the zero-length
>         array.

What about the XFAIL in gcc.dg/array-5.c?

Franz.

  reply	other threads:[~2001-09-20  2:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-14 12:54 DJ Delorie
2001-09-14 14:41 ` Richard Henderson
2001-09-14 14:47   ` DJ Delorie
2001-09-14 14:50     ` Richard Henderson
2001-09-14 18:33   ` DJ Delorie
2001-09-17 16:20     ` Richard Henderson
2001-09-19 12:21   ` DJ Delorie
2001-09-19 12:37     ` Richard Henderson
2001-09-19 12:44       ` DJ Delorie
2001-09-19 13:10       ` DJ Delorie
2001-09-19 13:36         ` Richard Henderson
2001-09-19 18:10           ` DJ Delorie
2001-09-20  2:04             ` Franz Sirl [this message]
2001-09-20  9:40               ` DJ Delorie
2001-09-20 14:06             ` Richard Henderson
2001-09-20 17:28               ` DJ Delorie
2001-09-20 18:00           ` Zack Weinberg
2001-09-20 18:11             ` DJ Delorie
2001-09-14 16:26 Richard Kenner

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=5.1.0.14.2.20010920110259.0248f4a8@mail.lauterbach.com \
    --to=franz.sirl-kernel@lauterbach.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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.
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).