James Greenhalgh writes:
> -For the generate pass, only the names of the insns matter, from either a
> -named @code{define_insn} or a @code{define_expand}. The compiler will
> +When expanding from gimple to RTL, only named @code{define_insn}
> +constructs and @code{define_expand} constructs are u
On Thu, Jan 08, 2015 at 02:43:27PM -0700, Jeff Law wrote:
> >A section that describes the lexical structure and syntax of .md files?
> Seems reasonable. However, is that too heavyweight?
>
> ISTM we have, effectively 3 items.
>
> Directives that start with an open-paren and end with their associa
On 01/06/15 11:55, Joseph Myers wrote:
On Tue, 6 Jan 2015, James Greenhalgh wrote:
-The @file{.md} file for a target machine contains a pattern for each
-instruction that the target machine supports (or at least each instruction
-that is worth telling the compiler about). It may also contain c
On Tue, 6 Jan 2015, James Greenhalgh wrote:
> > -The @file{.md} file for a target machine contains a pattern for each
> > -instruction that the target machine supports (or at least each instruction
> > -that is worth telling the compiler about). It may also contain comments.
> > -A semicolon caus
As requested, please find a paragraph-by-paragraph justification for
the changes in this patch below.
I hope this aids review.
Of particular interest for this patch is the removal of the text
describing the semicolon for a comment syntax. I believe that a
description of the syntax of a .md file d
