public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34302] [4.3 regression] Invalid code reordering
Date: Mon, 10 Dec 2007 21:33:00 -0000 [thread overview]
Message-ID: <20071210213250.3812.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34302-50@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from zadeck at naturalbridge dot com 2007-12-10 21:32 -------
Subject: Re: [4.3 regression] Invalid code reordering
Richard Guenther wrote:
> On Dec 10, 2007 9:46 PM, Kenneth Zadeck <zadeck@naturalbridge.com> wrote:
>
>> This patch fixes where the move insn is inserted on pre increments. it
>> had been inserted before the auto inc but this is not correct. it needs
>> to replace the existing add to properly handle the case where the
>> operands of the add change between the add and the load.
>>
>> Tested on ppc-32. The patch will only effect architectures with pre
>> increment.
>>
>> Ok for commit?
>>
>
> This is ok.
>
> Thanks,
> Richard.
>
>
>> Jakub, note that i changed the name of your testcase from 20071012-1.c
>> to 20071210-1.c.
>> I believe that this is the correct.
>>
>> Kenny
>>
>>
>> 2007-12-10 Kenneth Zadeck <zadeck@naturalbridge.com>
>>
>> PR rtl-optimization/34302
>> * auto-inc-dec.c (attempt_change): Change place where move is
>> inserted.
>>
>> 2007-12-10 Jakub Jelinek <jakub@redhat.com>
>>
>> PR rtl-optimization/34302
>> * gcc.c-torture/execute/20071210-1.c: New test.
>>
>>
>>
committed as revision 130751
Kenny
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34302
prev parent reply other threads:[~2007-12-10 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 13:18 [Bug target/34302] New: " schwab at suse dot de
2007-11-30 13:21 ` [Bug target/34302] " schwab at suse dot de
2007-11-30 14:17 ` [Bug rtl-optimization/34302] " schwab at suse dot de
2007-11-30 15:33 ` zadeck at naturalbridge dot com
2007-11-30 15:37 ` schwab at suse dot de
2007-12-01 13:55 ` zadeck at naturalbridge dot com
2007-12-01 17:22 ` schwab at suse dot de
2007-12-02 21:47 ` pinskia at gcc dot gnu dot org
2007-12-10 18:01 ` jakub at gcc dot gnu dot org
2007-12-10 18:15 ` zadeck at naturalbridge dot com
2007-12-10 19:35 ` jakub at gcc dot gnu dot org
2007-12-10 20:02 ` zadeck at naturalbridge dot com
2007-12-10 20:47 ` zadeck at naturalbridge dot com
2007-12-10 20:57 ` richard dot guenther at gmail dot com
2007-12-10 21:32 ` zadeck at gcc dot gnu dot org
2007-12-10 21:33 ` zadeck at naturalbridge dot com
2007-12-10 21:33 ` zadeck at naturalbridge dot com [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=20071210213250.3812.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).