public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24315] [3.4 Regression] amd64 fails -fpeephole2
Date: Thu, 10 Nov 2005 07:27:00 -0000 [thread overview]
Message-ID: <20051110072753.10467.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24315-11506@http.gcc.gnu.org/bugzilla/>
------- Comment #16 from uros at gcc dot gnu dot org 2005-11-10 07:27 -------
Subject: Bug 24315
Author: uros
Date: Thu Nov 10 07:27:47 2005
New Revision: 106728
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=106728
Log:
PR target/24315
* config/i386/i386.md (*pushdi2_rex64 splitter)
(*movdi_1_rex64 splitter): Delay splitting after
flow2 pass only when (optimize > 0 && flag_peephole2).
PR target/19340
* reg-stack.c (reg_to_stack): Update register liveness also
for flag_sched2_use_traces.
testsuite/
PR target/24315
* gcc.dg/pr24315.c: New test.
PR target/19340
* gcc.dg/pr19340.c: New test.
Added:
branches/gcc-3_4-branch/gcc/testsuite/gcc.dg/pr19340.c
- copied unchanged from r106632, trunk/gcc/testsuite/gcc.dg/pr19340.c
branches/gcc-3_4-branch/gcc/testsuite/gcc.dg/pr24315.c
Modified:
branches/gcc-3_4-branch/gcc/ChangeLog
branches/gcc-3_4-branch/gcc/config/i386/i386.md
branches/gcc-3_4-branch/gcc/reg-stack.c
branches/gcc-3_4-branch/gcc/testsuite/ChangeLog
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24315
next prev parent reply other threads:[~2005-11-10 7:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 18:57 [Bug c/24315] New: " erg at trifocus dot net
2005-10-11 18:59 ` [Bug target/24315] " erg at trifocus dot net
2005-10-11 19:00 ` pinskia at gcc dot gnu dot org
2005-10-11 19:03 ` erg at trifocus dot net
2005-10-11 19:05 ` pinskia at gcc dot gnu dot org
2005-10-11 19:28 ` pinskia at gcc dot gnu dot org
2005-10-12 13:30 ` pinskia at gcc dot gnu dot org
2005-10-12 13:33 ` pinskia at gcc dot gnu dot org
2005-10-12 13:42 ` [Bug target/24315] [3.4/4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-10-12 13:45 ` pinskia at gcc dot gnu dot org
2005-10-12 13:46 ` pinskia at gcc dot gnu dot org
2005-10-12 13:48 ` pinskia at gcc dot gnu dot org
2005-10-17 7:09 ` cvs-commit at gcc dot gnu dot org
2005-10-17 7:21 ` [Bug target/24315] [3.4/4.0 " uros at kss-loka dot si
2005-11-08 7:59 ` uros at gcc dot gnu dot org
2005-11-08 8:19 ` [Bug target/24315] [3.4 " bonzini at gcc dot gnu dot org
2005-11-10 7:27 ` uros at gcc dot gnu dot org [this message]
2005-11-10 7:31 ` uros at kss-loka dot si
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=20051110072753.10467.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).