public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [hsa] HSA: add support for function declaration emission and, fix RA.
Date: Tue, 30 Jun 2015 13:33:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1506301526320.23227@wotan.suse.de> (raw)
In-Reply-To: <5592974A.5020904@suse.cz>

[-- Attachment #1: Type: text/plain, Size: 460 bytes --]

Hi,

On Tue, 30 Jun 2015, Martin Liška wrote:

> Following patch implements emission of function declarations and removes 
> hsa_call_block_insn. The insn is replaced with a new hsa_arg_block_insn, 
> which will make insn iteration flat and much easier for register 
> allocator.

Given that BRIG forces us to have a multi-level layering of instructions 
in one way or the other, I indeed think this new representation is nicer, 
so thanks.


Ciao,
Michael.

  reply	other threads:[~2015-06-30 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 13:20 Martin Liška
2015-06-30 13:33 ` Michael Matz [this message]
2015-06-30 13:36   ` Martin Liška

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=alpine.LSU.2.20.1506301526320.23227@wotan.suse.de \
    --to=matz@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /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).