This is the mail archive of the gcc@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]
Other format:	[Raw text]

Re: subreg_get_info vs mode restrictions in registers?

From: DJ Delorie <dj at redhat dot com>
To: iant at google dot com
Cc: gcc at gcc dot gnu dot org
Date: Wed, 24 Jan 2007 16:42:16 -0500
Subject: Re: subreg_get_info vs mode restrictions in registers?
References: <200701242041.l0OKfsL3029775@greed.delorie.com> <m3tzygkt2l.fsf@localhost.localdomain>

> So can you expand on what is actually going wrong?

At the moment, the problem is divide by zero - nregs_ymode is zero.

IIRC the problem before was that reload kept choosing $r2 or $r3 for
pseudos that were QImode.  Since the m32c is already register starved,
this leads to unfixable situations.

References:
- subreg_get_info vs mode restrictions in registers?
  - From: DJ Delorie
- Re: subreg_get_info vs mode restrictions in registers?
  - From: Ian Lance Taylor

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