From: Thomas Sailer <sailer@ife.ee.ethz.ch>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Kaoru Fukui <k_fukui@highway.ne.jp>,
linuxppc-dev@lists.linuxppc.org, gcc@gcc.gnu.org
Subject: Re: kerne-2.4.0-test13pre3 with gcc-2.97
Date: Sun, 24 Dec 2000 16:19:23 +0100 [thread overview]
Message-ID: <3A4613FB.384BAD24@ife.ee.ethz.ch> (raw)
In-Reply-To: or66kazecj.fsf@guarana.lsd.ic.unicamp.br
Alexandre Oliva wrote:
>
> On Dec 23, 2000, Kaoru Fukui <k_fukui@highway.ne.jp> wrote:
>
> > - unsigned char b[0];
> > + unsigned char *b;
>
> This change (and apparently all other changes you've made) are
> definitely wrong. Zero-sized arrays as the last element of a
> structure used to be an extension in GCC 2.95.2, that has been adopted
> by C99 with a slightly different syntax, that GCC CVS supports: just
> remove the `0' from between the braces.
Which is not backward compatible, unfortunately. So the
backward compatible fix would be "unsigned char b[1];".
Tom
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-24 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 5:52 kerne-2.4.0-test13pre3 with gcc-2.97 Kaoru Fukui
[not found] ` <20001223142145.T5858@coruscant.gnumonks.org>
2000-12-23 13:30 ` Kaoru Fukui
2000-12-24 3:29 ` Alexandre Oliva
2000-12-24 13:53 ` Kaoru Fukui
2000-12-24 15:20 ` Thomas Sailer
2000-12-24 15:19 ` Thomas Sailer [this message]
2000-12-24 18:08 ` Alexandre Oliva
2000-12-26 1:41 ` how to use macro in assemble language embedded in C? kerler
[not found] ` <20001226221757.Postino-028251@smtp01.highway.ne.jp>
2000-12-27 3:33 ` kerler
2000-12-27 15:50 ` Alexandre Oliva
2000-12-27 23:37 ` kerne-2.4.0-test13pre3 with gcc-2.97 Richard Henderson
2000-12-24 15:16 ` Thomas Sailer
-- strict thread matches above, loose matches on Subject: below --
2000-12-25 0:04 Kaoru Fukui
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=3A4613FB.384BAD24@ife.ee.ethz.ch \
--to=sailer@ife.ee.ethz.ch \
--cc=aoliva@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).