[PATCH] configuration support for rtl flag checking

[Zack Weinberg]

On Tue, May 07, 2002 at 05:28:13PM -0700, Janis Johnson wrote:
> On Tue, May 07, 2002 at 05:12:32PM -0700, Zack Weinberg wrote:
> > On Tue, May 07, 2002 at 03:53:26PM -0700, Janis Johnson wrote:
> > >     ../../gcc-mainline/gcc/crtstuff.c:263: RTL flag check: access macro
> > >     used with unexpected rtx code `reg' in get_subtarget, at expr.c:3615
> > >     Please submit a full bug report,
> > >     with preprocessed source if appropriate.
> > 
> > You should maybe make the failure message say which flag it was, as
> > well as which RTX code was unexpected.
> 
> The message gives the location where the macro was used and the code of
> the rtx that was unexpectedly used with the macro.  Knowing the flag
> isn't as important as knowing the macro, since each flag is accessed by
> several macros.  It also didn't seem important to list all of the
> possible expected code values, since there are between one and eight of
> those and it's easy enough to get that information from the macro
> definition.

Well, I'd still like to see the name of the access macro:

 .../crtstuff.c:263: RTL flag check: RTX_UNCHANGING_P used with
 unexpected rtx code `reg' in get_subtarget, at expr.c:3615

Imagine the problem's buried in one of those monstrous conditionals we
have; finding it is going to be easier the more information we get in
the error message.

zw