James Greenhalgh writes:
> @node Example
> @section Example of @code{define_insn}
> @cindex @code{define_insn} example
>
> -Here is an actual example of an instruction pattern, for the 68000/68020.
> +Here is an example of an instruction pattern, taken from the machine
> +description for the
On Thu, Jan 08, 2015 at 10:00:02PM +, Jeff Law wrote:
> On 01/06/15 04:21, James Greenhalgh wrote:
> If I havne't commented, then those hunks should be considered OK -- you
> can check those hunks in if you want.
Thanks Jeff,
I've committed the attached as revision 219432. I'll work on respi
On Thu, Jan 08, 2015 at 03:00:02PM -0700, Jeff Law wrote:
> On 01/06/15 04:21, James Greenhalgh wrote:
> >-A @code{define_insn} is an RTL expression containing four or five
> >operands:
> >+A @code{define_insn} contains either four or five components:
> How about
> A @code{define_insn} contains th
On 01/06/15 04:21, James Greenhalgh wrote:
Hi,
This patch updates the second section of md.texi - "Everything about
Patterns".
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
Hi,
This patch updates the second section of md.texi - "Everything about
Patterns".
I was aiming to:
* Remove outdated details of the compiler.
* Remove long or obscure words that, while accurate, only served to
obfuscate a simple idea.
* Refer to similar things in a consistent fashio
