This is the mail archive of the gcc-help@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: GCC internals - Instruction Patterns

From: Jeff Law <law at redhat dot com>
To: htio2 <wenbin dot leong at gmail dot com>, gcc-help at gcc dot gnu dot org
Date: Mon, 5 Oct 2015 22:32:33 -0600
Subject: Re: GCC internals - Instruction Patterns
Authentication-results: sourceware.org; auth=none
References: <1444096584208-1191730 dot post at n5 dot nabble dot com> <56132B92 dot 2060808 at redhat dot com> <1444104903411-1191748 dot post at n5 dot nabble dot com>

On 10/05/2015 10:15 PM, htio2 wrote:

Ok, so you mean this non standard patterns is not use by compiler ?

If they start with a "*" the patterns can not be referenced by thecompiler directly, but if code which matches the structure of thosepatterns is created, then those patterns will be used. Examples wouldbe all the *movXX_internal patterns in the v850 machine description.

A non-standard name which does not start with a "*" can be referenced bythe target to generate code. Since you seem to be looking at the v850backend, an example would be the "save_interrupt" pattern which the v850backend can reference via gen_save_interrupt.

All this is explained in detail in the GCC internals manual. Irecommend you read it carefully.


jeff

Follow-Ups:
- Re: GCC internals - Instruction Patterns
  - From: htio2

References:
- GCC internals - Instruction Patterns
  - From: htio2
- Re: GCC internals - Instruction Patterns
  - From: Jeff Law
- Re: GCC internals - Instruction Patterns
  - From: htio2

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