From: Anton Altaparmakov <aia21@cantab.net>
To: ivangurdiev@linuxfreemail.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Compiler question....
Date: Tue, 21 May 2002 09:29:54 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20020521092734.01fe4d30@pop.cus.cam.ac.uk> (raw)
In-Reply-To: <02052019404000.15624@cobra.linux>
At 02:40 21/05/02, Ivan Gyurdiev wrote:
>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?
I consider it a bug in the compiler. The gcc folk have not replied to my
filed bug report yet so I have no idea if they agree or not...
The error messages the compiler is generating are completely bogus because
the unnamed fields ARE of type struct or union. It's just that they are
typedeffed so that the words "struct" and "union" do not appear. IMO that
is a screwup by gcc...
Best regards,
Anton
>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
--
"I've not lost my mind. It's backed up on tape somewhere." - Unknown
--
Anton Altaparmakov <aia21 at cantab.net> (replace at with @)
Linux NTFS Maintainer / IRC: #ntfs on irc.openprojects.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2002-05-21 8:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 1:40 Ivan Gyurdiev
2002-05-21 8:29 ` Anton Altaparmakov [this message]
2002-05-21 15:49 Ed Vance
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.20020521092734.01fe4d30@pop.cus.cam.ac.uk \
--to=aia21@cantab.net \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®