All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivangurdiev@linuxfreemail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Compiler question....
Date: Mon, 20 May 2002 19:40:40 -0600	[thread overview]
Message-ID: <02052019404000.15624@cobra.linux> (raw)

Kernel 2.5.17

Should the compiler be blamed or the code?
gcc 2.96 compiles it. 3.1 won't.
Before people yell at me to use the recommended compiler, I would like to say
that it really wouldn't solve the problem. Compilers move forward, the code 
has to comply. Therefore I'm excersing my right to ignore all warnings about 
my compiler and use it. If this is a bug in the compiler, I'd agree and 
switch back to 2.96. Otherwise I'd suggest the code be changed.
Comments or advice?

In file included from attrib.h:31,
                 from debug.h:31,
                 from ntfs.h:40,
                 from aops.c:29:
layout.h:299: unnamed fields of type other than struct or union are not 
allowed
layout.h:1450: unnamed fields of type other than struct or union are not 
allowed
layout.h:1466: unnamed fields of type other than struct or union are not 
allowed
layout.h:1715: unnamed fields of type other than struct or union are not 
allowed
layout.h:1892: unnamed fields of type other than struct or union are not 
allowed
layout.h:2052: unnamed fields of type other than struct or union are not 
allowed
layout.h:2064: unnamed fields of type other than struct or union are not 
allowed

             reply	other threads:[~2002-05-21  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21  1:40 Ivan Gyurdiev [this message]
2002-05-21  8:29 ` Compiler question Anton Altaparmakov
  -- strict thread matches above, loose matches on Subject: below --
2002-05-21 15:49 Ed Vance
2006-10-05 13:29 Compiler Question wei.li4
2006-10-05 14:28 ` Becky Bruce

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=02052019404000.15624@cobra.linux \
    --to=ivangurdiev@linuxfreemail.com \
    --cc=linux-kernel@vger.kernel.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 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.