This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: [testsuite] i386 reload issue

To: Richard Henderson <rth at cygnus dot com>
Subject: Re: [testsuite] i386 reload issue
From: Jakub Jelinek <jakub at redhat dot com>
Date: Fri, 25 Aug 2000 18:12:38 -0400
Cc: gcc-patches at gcc dot gnu dot org
References: <20000824111849.B21753@devserv.devel.redhat.com> <20000825150107.A24731@cygnus.com>
Reply-To: Jakub Jelinek <jakub at redhat dot com>

On Fri, Aug 25, 2000 at 03:01:07PM -0700, Richard Henderson wrote:
> On Thu, Aug 24, 2000 at 11:18:49AM -0400, Jakub Jelinek wrote:
> > In the following case on ia32, reload will replace a (mem:QI (reg) ) in a
> > call_value_1 with (mem:QI (const_int 0)) and the result is call *$0
> > which the assembler does not like at all.
> > Ok to commit?
> 
> I can't replicate this with today's sources.  Does it still
> fail for you?

Unless it changed during last 6 commits (I have my commit to i386.c as last
in my tree), it should still fail.
Will update now and retry.
By chance, were you testing crash21.C from testsuite and not the one I
posted? crash21.C was already in the testsuite, so I have commited it as
crash22.C.

	Jakub

References:
- [testsuite] i386 reload issue
  - From: Jakub Jelinek
- Re: [testsuite] i386 reload issue
  - From: Richard Henderson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]