From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: gcc@gcc.gnu.org
Subject: ra-colorize.c:1068: `inv_reg_alloc_order' undeclared
Date: Wed, 24 Jul 2002 16:05:00 -0000 [thread overview]
Message-ID: <200207241916.g6OJGF5F016657@hiauly1.hia.nrc.ca> (raw)
The following error occurs building a vax-ultrix cross:
gcc -c -DIN_GCC -DCROSS_COMPILE -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/ra-colorize.c -o ra-colorize.o
../../gcc/gcc/ra-colorize.c: In function `get_free_reg':
../../gcc/gcc/ra-colorize.c:1068: `inv_reg_alloc_order' undeclared (first use in this function)
../../gcc/gcc/ra-colorize.c:1068: (Each undeclared identifier is reported only once
The error occurs because inv_reg_alloc_order is only defined when
REG_ALLOC_ORDER is defined. None of the vax ports define this macro.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2002-07-24 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 16:05 John David Anglin [this message]
2002-07-24 20:27 ` [fix] for: " Michael Matz
2002-07-24 21:48 ` John David Anglin
2002-07-24 22:44 ` Michael Matz
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=200207241916.g6OJGF5F016657@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--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).