From: Grant Grundler <grundler@cup.hp.com>
To: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] Internal compiler error
Date: Wed, 12 Jul 2000 11:26:37 -0700 (PDT) [thread overview]
Message-ID: <200007121826.LAA14363@milano.cup.hp.com> (raw)
Dave (dhd),
Since you expressed an interest in compiler bugs:
...
make[1]: Leaving directory `/linux/grundler/linux-2.3/arch/parisc/hpux'
hppa-linux-gcc -I/linux/grundler/linux-2.3/include -D__KERNEL__ -I/linux/grundler/linux-2.3/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -ffunction-sections -D__linux__ -pipe -fno-strength-reduce -DUTS_MACHINE='"parisc"' -c -o init/version.o init/version.c
dino.c: In function `dino_common_init':
dino.c:675: incompatible type for argument 2 of `list_add'
dino.c:675: Tree check: expected class 't', have 'x' (error_mark)
dino.c:675: Internal compiler error in `expand_inline_function', at integrate.c:678
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
make[3]: *** [dino.o] Error 1
make[3]: Leaving directory `/linux/grundler/linux-2.3/drivers/gsc'
...
I'm changing code in several files in order to build an I/O tree of hp_devices
much like pci does...the problem above was due to one of my changes:
...
STATIC struct list_head dino_list;
...
list_add(&dino_dev->dino_hba.hba_dev->global_list, dino_list);
Missing a '&' in front of dino_list and the compiler really
didn't like that. I don't have a big problem with the compiler
"oops"ing here since it correctly identified the problem.
cheers,
grant
next reply other threads:[~2000-07-12 18:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 18:26 Grant Grundler [this message]
2000-07-12 18:35 ` [parisc-linux] Internal compiler error John David Anglin
2000-07-12 19:17 ` Grant Grundler
2000-07-12 18:15 ` willy
2000-07-12 19:43 ` John David Anglin
2000-07-12 19:37 ` John David Anglin
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=200007121826.LAA14363@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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 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.