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: Finding out what backend instruction pattern matches instruction

From: Ian Lance Taylor <iant at google dot com>
To: Andrew Hutchinson <andrewhutchinson at cox dot net>
Cc: gcc at gcc dot gnu dot org
Date: 22 Jan 2008 17:54:00 -0800
Subject: Re: Finding out what backend instruction pattern matches instruction
References: <4794DD64.9040109@cox.net> <m33aspabte.fsf@localhost.localdomain> <47968971.8000100@cox.net>

Andrew Hutchinson <andrewhutchinson@cox.net> writes:

> As I say above, the logic already exists as c function. If we could
> call these directly to determine the attribute value, it would be much
> easier!

You can.  Use symbol_ref.  Again, examples in mips.md.  Note how the
default value for the "length" attribute can call
mips_load_store_insns.

Ian

References:
- Finding out what backend instruction pattern matches instruction
  - From: Andrew Hutchinson
- Re: Finding out what backend instruction pattern matches instruction
  - From: Ian Lance Taylor
- Re: Finding out what backend instruction pattern matches instruction
  - From: Andrew Hutchinson

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