From: Peter Jordan <pjordan@noname.blackwire.com>
To: gcc@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org
Subject: re: subscripted value is neither array nor pointer
Date: Mon, 13 Mar 2000 00:47:00 -0000 [thread overview]
Message-ID: <20000313005405.A30993@noname.blackwire.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]
>> t-> osd2.linux2.l_i_reserved2[0] =
>Take a look at the preprocessed code first, it may turn out to be some
>preprocessing issue, such as the wrong header file getting included or
>something.
Urk. I thought it might have been a known "change" and not a bug.
Here goes ...
Reading specs from /usr/lib/gcc-lib/i686-pc-linux-gnu/2.96/specs
gcc version 2.96 20000306 (experimental)
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.96/cpp -lang-c -v -I../../lib -I../../lib -D__GNUC__=2 -D__GNUC_MINOR__=96 -D__GNUC_PATCHLEVEL__=0 -D__ELF__ -Dunix -Dlinux -D__ELF__ -D__unix__ -D__linux__ -D__unix -D__linux -Asystem(posix) -D__OPTIMIZE__ -g -Acpu(i386) -Amachine(i386) -Di386 -D__i386 -D__i386__ -D__tune_pentiumpro__ -DHAVE_LINUX_FS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDARG_H=1 -DHAVE_ERRNO_H=1 -DHAVE_MALLOC_H=1 -DHAVE_MNTENT_H=1 -DHAVE_PATHS_H=1 -DHAVE_DIRENT_H=1 -DHAVE_GETOPT_H=1 -DHAVE_SETJMP_H=1 -DHAVE_SIGNAL_H=1 -DHAVE_TERMIOS_H=1 -DHAVE_LINUX_FD_H=1 -DHAVE_LINUX_MAJOR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_NET_IF_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_VPRINTF=1 -DSIZEOF_SHORT=2 -DSIZEOF_INT=4 -DSIZEOF_LONG=4 -DSIZEOF_LONG_LONG=8 -DHAVE_GETRUSAGE=1 -DHAVE_LLSEEK=1 -DHAVE_STRDUP=1 -DHAVE_STRCASECMP=1 -DHAVE_SRANDOM=1 -DHAVE_FCHOWN=1 -DHAVE_MALLINFO=1 -DHAVE_INO_T=1 -DHAVE_EXT2_IOCTLS=1 swapfs.c swapfs.i
GNU CPP version 2.96 20000306 (experimental) (cpplib)
(i386 Linux/ELF)
ignoring duplicate directory `../../lib'
#include "..." search starts here:
#include <...> search starts here:
../../lib
/usr/local/include
/usr/i686-pc-linux-gnu/include
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.96/include
/usr/include
End of search list.
/usr/lib/gcc-lib/i686-pc-linux-gnu/2.96/cc1 swapfs.i -quiet -dumpbase swapfs.c -g -O2 -version -o swapfs.s
GNU C version 2.96 20000306 (experimental) (i686-pc-linux-gnu) compiled by GNU C version 2.96 20000306 (experimental).
swapfs.c: In function `ext2fs_swap_inode':
swapfs.c:119: subscripted value is neither array nor pointer
swapfs.c:120: subscripted value is neither array nor pointer
swapfs.c:121: subscripted value is neither array nor pointer
swapfs.c:122: subscripted value is neither array nor pointer
[-- Attachment #2: swapfs.i.gz --]
[-- Type: application/x-gzip, Size: 15466 bytes --]
next reply other threads:[~2000-03-13 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-13 0:47 Peter Jordan [this message]
2000-03-13 1:04 ` Alexandre Oliva
2000-03-13 2:28 ` subscripted value is neither array nor pointer(close?) PJ
2000-03-13 4:21 ` tytso
2000-03-13 2:50 ` subscripted value (../../lib vs. ../../../lib explained) PJ
-- strict thread matches above, loose matches on Subject: below --
2000-03-12 22:46 subscripted value is neither array nor pointer Peter Jordan
2000-03-12 22:59 ` Alexandre Oliva
2000-03-13 2:36 ` Andreas Schwab
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=20000313005405.A30993@noname.blackwire.com \
--to=pjordan@noname.blackwire.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@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).