public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Christopher Matthews <chrismatthews@google.com>
Cc: Aldy Hernandez <aldyh@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [tuples] adding gimple_asm
Date: Fri, 03 Aug 2007 14:33:00 -0000	[thread overview]
Message-ID: <46B33CA1.3000905@google.com> (raw)
In-Reply-To: <5794c4c80708022105w68072b23scdd10346e194d8ec@mail.gmail.com>

On 8/3/07 12:05 AM, Christopher Matthews wrote:

> +/* Test GIMPLE_ASSIGN.  */ 

s/GIMPLE_ASSIGN/GIMPLE_ASM/

> [ ... ]
> +/* { dg-final { scan-tree-dump-times ":\\\"%eax\\\"" 1 "gimple"} } */
> +

You need to add a cleanup action in all the test cases:

/* { dg-final { cleanup-tree-dump "gimple" } } */

> +dump_gimple_asm (pretty_printer *buffer, gimple gs, int spc, int flags)
> +{
> + unsigned int i;
> + newline_and_indent (buffer, spc);
> + pp_string (buffer, "asm {");
> + newline_and_indent (buffer, spc + 2);

Better follow the format used to dump ASM_EXPRs (see the ASM_EXPR case
in tree-pretty-print.c:dump_generic_node).

> +/* Helper function to set the simple fields of a asm stmt. */
> +

Need documentation for arguments.

> +gimple
> +build_gimple_asm_1 (const char *string, unsigned ninputs, unsigned noutputs,

Better declare static.  It will not be called from outside.

> + CLOBBERS is a vector of the clobbered register parameters.
> + */

Closing comment at end of previous line.

> +
> + p = build_gimple_asm_1(string, ninputs, noutputs, nclobbers);

Space before '('.


OK with those changes.

  reply	other threads:[~2007-08-03 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  4:06 Christopher Matthews
2007-08-03 14:33 ` Diego Novillo [this message]
2007-08-03 16:08   ` Aldy Hernandez
2007-08-07  1:30     ` Christopher Matthews
2007-08-07 14:25       ` Diego Novillo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B33CA1.3000905@google.com \
    --to=dnovillo@google.com \
    --cc=aldyh@redhat.com \
    --cc=chrismatthews@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).