On 10/15/2012 06:41 AM, Joern Rennecke wrote:
> The following patch is still awaiting review:
>
> 2011-09-19 J"orn Rennecke
>
> * genoutput.c (process_template): Process '*' in '@' alternatives.
> * doc/md.texi (node Output Statement): Provide example for the
> above.
>
> http
The following patch is still awaiting review:
2011-09-19 J"orn Rennecke
* genoutput.c (process_template): Process '*' in '@' alternatives.
* doc/md.texi (node Output Statement): Provide example for the above.
http://gcc.gnu.org/ml/gcc-patches/2012-09/msg01422.html
The following patch is still awaiting review:
2011-09-19 J"orn Rennecke
* genoutput.c (process_template): Process '*' in '@' alternatives.
* doc/md.texi (node Output Statement): Provide example for the above.
http://gcc.gnu.org/ml/gcc-patches/2012-09/msg01422.html
Quoting Georg-Johann Lay :
+ * return stack_mem_p (operands[0]) ? \"push 0" : \"clrmem %0\";
---^
Isn't there a backslash missing?
Attached is the amended patch. Again, bootstrapped on i686-pc-linux-gnu .
2011-09-19 J"orn Rennecke
Quoting Georg-Johann Lay :
+ * return stack_mem_p (operands[0]) ? \"push 0" : \"clrmem %0\";
---^
Isn't there a backslash missing?
Oops, yes, there is.
Joern Rennecke a écrit:
Index: doc/md.texi
===
--- doc/md.texi (revision 191429)
+++ doc/md.texi (working copy)
@@ -665,6 +665,22 @@ (define_insn ""
@end group
@end smallexample
+If you just need a little bit of C code in one (or
Quoting Richard Guenther :
Something smaller (but pointless) woudl be nice.
I have attached the patch with the example added to the documentation.
Again, bootstrapped on i686-pc-linux-gnu.
2011-09-19 J"orn Rennecke
* genoutput.c (process_template): Process '*' in '@' alternatives.
On Wed, Sep 19, 2012 at 2:06 PM, Joern Rennecke wrote:
> Quoting Richard Guenther :
>
>
>> I think that needs to be documented somewhere in the internals manual,
>
>
> I suppose it should logically go to the current end of the Output Statement
> node in md.texi . Line 668 in revision 191429, just
Quoting Richard Guenther :
I think that needs to be documented somewhere in the internals manual,
I suppose it should logically go to the current end of the Output
Statement node in md.texi . Line 668 in revision 191429, just before
the Predicates
node.
possibly with an example.
AFA
On Wed, Sep 19, 2012 at 3:51 AM, Joern Rennecke wrote:
> I am about to submit the ARCompact target port; this port needs a few
> patches to target-independent code.
>
> There is a move pattern with 20 alternatives; a few of them need a simple
> function call to decide which output pattern to use.
I am about to submit the ARCompact target port; this port needs a few
patches to target-independent code.
There is a move pattern with 20 alternatives; a few of them need a simple
function call to decide which output pattern to use. With the '@'-syntax
for multi-alternative templates, each alter
11 matches
Mail list logo
