Date: Wed, 10 Sep 2003 17:41:35 -0700 From: Scott Reese <sreese@codysbooks.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: Internal compiler error in reload_cse_simplify_operands Message-ID: <1063240895.37828.20.camel@borges> In-Reply-To: <20030911002245.GA30852@troutmask.apl.washington.edu> References: <1063228474.9366.10.camel@borges> <1063236870.37828.5.camel@borges> <20030910234012.GA30618@troutmask.apl.washington.edu> <1063237547.37828.14.camel@borges> <20030911002245.GA30852@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2003-09-10 at 17:22, Steve Kargl wrote:
> On Wed, Sep 10, 2003 at 04:45:47PM -0700, Scott Reese wrote:
> > On Wed, 2003-09-10 at 16:40, Steve Kargl wrote:
> > > On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
> > > > On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
> > > > >
> > > > > I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a PIII
> > > > > 800 MHz processor with 256 MB RAM to a PIV 2.4 GHz processor and VIA P4B
> > > > > 400 motherboard with 512 MB RAM. The system starts and runs great, but
> > > > > I can't build anything with it anymore.
> > >
> > > Did you have these errors with your PIII 800 MHz processor and
> > > 256 MB of RAM? If the answer is no, the old harware wsa rock solid,
> > > then I suspect you have a hardware problem. For example, power
> > > supply can't supply enough power or the memory isn't seated correctly
> > > or insufficient heat sinking on the CPU or ...
> >
> > No, I didn't have these errors with the old hardware. It seemed very
> > solid to me. I would be extremely disappointed if this were a hardware
> > failure of some kind as I just got it upgraded this morning. :/
> >
> > One question, though...Doesn't flakey hardware usually cause *random*
> > errors? I ask because the error I'm receiving upon issuing 'make
> > buildworld' is recurring in exactly the same place every time. I'm
> > wondering if something somewhere got hosed...
>
> I deleted your original email, but I thought you said that
> you got ICE's while building a couple of ports. Do you
> set CFLAGS and/or CPUTYPE to some strange combination of
> options?
I have no CFLAGS set and CPUTYPE is also not set. Just successfully
built world, but the kernel compilation stopped with another ICE...the
same one I got earlier today when trying to build a kernel:
/usr/src/sys/dev/aic7xxx/aic79xx.c: In function `ahd_run_data_fifo':
/usr/src/sys/dev/aic7xxx/aic79xx.c:787: error: unrecognizable insn:
(insn 1427 1422 1440 48 0x284a9420 (parallel [
(set (reg/v:QI 4 sil [363])
(asm_operands/v:QI ("inb %%dx,%0") ("=a") 0 [
(reg/v:SI 1 edx [361])
]
[
(asm_input:SI ("d"))
] ("machine/cpufunc.h") 197))
(clobber (reg:QI 19 dirflag))
(clobber (reg:QI 18 fpsr))
(clobber (reg:QI 17 flags))
]) -1 (insn_list 1422 (nil))
(nil))
/usr/src/sys/dev/aic7xxx/aic79xx.c:787: internal compiler error: in
reload_cse_simplify_operands, at reload1.c:8345
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html>; for instructions.
*** Error code 1
Stop in /usr/obj/usr/src/sys/BORGES.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
Guess maybe it's hardware-related. Was hoping to find a solution that
would clear any charges against my new hardware, but I guess that's all
that's left. *sigh*
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1063240895.37828.20.camel>