From: Pete Popov <ppopov@mvista.com>
To: Karel van Houten <K.H.C.vanHouten@research.kpn.com>
Cc: Ralf Baechle <ralf@oss.sgi.com>, Adrian Bunk <bunk@fs.tum.de>,
linux-mips@oss.sgi.com,
Daniel Jacobowitz <djacobowitz@mvista.com>
Subject: Re: Compile error with current CVS kernel
Date: Tue, 13 Mar 2001 13:15:19 -0800 [thread overview]
Message-ID: <3AAE8DE7.D6F5AB9E@mvista.com> (raw)
In-Reply-To: 200103131840.TAA14996@sparta.research.kpn.com
Karel van Houten wrote:
>
> While I wrote my previous mail:
>
> {standard input}: Assembler messages:
> {standard input}:1993: Error: expression too complex
> {standard input}:1993: Fatal error: internal Error, line 1823, ./config/tc-mips.c
> make[3]: *** [vgacon.o] Error 1
>
> Again.... :-(
We encountered this exact problem a few days ago. One of our engineers
tracked it down to the combination of complex macros and inline
functions in arch/mips/io.h. He pinpointed precisely the problem to a
rare gcc "bug", which is not likely to get fixed anytime soon. I believe
a patch was already submitted to Ralf, but it will have to get tested.
Pete
next prev parent reply other threads:[~2001-03-13 21:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 21:56 Compile error with current CVS kernel Adrian Bunk
2001-03-12 21:56 ` Adrian Bunk
2001-03-12 23:15 ` Ralf Baechle
2001-03-12 23:15 ` Ralf Baechle
2001-03-13 7:46 ` Houten K.H.C. van (Karel)
2001-03-13 13:53 ` Ralf Baechle
2001-03-13 14:22 ` Ralf Baechle
2001-03-13 18:18 ` Karel van Houten
2001-03-13 18:18 ` Karel van Houten
2001-03-13 18:27 ` Ralf Baechle
2001-03-13 18:27 ` Ralf Baechle
2001-03-13 18:38 ` Karel van Houten
2001-03-13 18:38 ` Karel van Houten
2001-03-13 18:40 ` Karel van Houten
2001-03-13 18:40 ` Karel van Houten
2001-03-13 21:15 ` Pete Popov [this message]
2001-03-21 17:39 ` Adrian Bunk
2001-03-21 17:39 ` Adrian Bunk
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=3AAE8DE7.D6F5AB9E@mvista.com \
--to=ppopov@mvista.com \
--cc=K.H.C.vanHouten@research.kpn.com \
--cc=bunk@fs.tum.de \
--cc=djacobowitz@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox