public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Denis Chertykov <chertykov@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: Richard Henderson <rth@redhat.com>,
	gcc-patches@gcc.gnu.org, 	Anatoly Sokolov <aesok@post.ru>,
	Eric Weddington <eric.weddington@atmel.com>
Subject: Re: [Patch,AVR]: Solve PR42210
Date: Sat, 04 Jun 2011 06:56:00 -0000	[thread overview]
Message-ID: <BANLkTikWtZE9Sxy5jqd+mYbSiRU4Tq6MbA@mail.gmail.com> (raw)
In-Reply-To: <4DE10E35.9040805@gjlay.de>

2011/5/28 Georg-Johann Lay <avr@gjlay.de>:
> Georg-Johann Lay wrote:
>>
>> Georg-Johann Lay wrote:
>>
>>> Richard Henderson wrote:
>>>
>>>
>>>> Why are you adding "optimize" to all these insns?  None of them will
>>>> be matched unless combine is run, which implies optimization.
>>>
>>> Here is a patch without optimize in the insn conditions.
>>>
>>> The optimize condition is still present in the insv expander because I
>>> do not know what the policy about that is in the avr backend.
>
> http://gcc.gnu.org/ml/gcc-patches/2011-04/msg02099.html
>
> Hi, I still have a patch hanging around and don't know what to do with it.
> Install, change (and if, how) or just throw away.
>

Please, commit it.

Denis.

      reply	other threads:[~2011-06-04  6:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 18:12 Georg-Johann Lay
2011-04-21 13:00 ` Georg-Johann Lay
2011-04-21 19:24   ` Richard Henderson
2011-04-26 12:59     ` Georg-Johann Lay
2011-04-26 15:28       ` Richard Henderson
2011-04-26 15:39         ` Georg-Johann Lay
2011-04-27 10:33         ` Georg-Johann Lay
2011-05-02  9:29           ` Ping #1: " Georg-Johann Lay
2011-05-16 18:33           ` Georg-Johann Lay
2011-05-28 19:09             ` Georg-Johann Lay
2011-06-04  6:56               ` Denis Chertykov [this message]

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=BANLkTikWtZE9Sxy5jqd+mYbSiRU4Tq6MbA@mail.gmail.com \
    --to=chertykov@gmail.com \
    --cc=aesok@post.ru \
    --cc=avr@gjlay.de \
    --cc=eric.weddington@atmel.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.com \
    /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).