public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bonzini at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/23453] [4.0/4.1 regression] miscompilation of PARI/GP on x86 with gcse after reload
Date: Fri, 14 Oct 2005 11:38:00 -0000 [thread overview]
Message-ID: <20051014113832.23863.qmail@sourceware.org> (raw)
In-Reply-To: <bug-23453-5724@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from bonzini at gcc dot gnu dot org 2005-10-14 11:38 -------
> gcse after reload may move loads from stack around stack pointer changes. here
> is simple workaround, it is supposed to prevent gcse after reload from touching
> expressions containing stack pointer at all.
Off the top of my head, if GCSE-after-reload is designed to remove redundant
spills, will it do *anything* with your patch?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23453
next parent reply other threads:[~2005-10-14 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23453-5724@http.gcc.gnu.org/bugzilla/>
2005-10-14 11:38 ` bonzini at gcc dot gnu dot org [this message]
2005-10-31 5:09 ` mmitchel at gcc dot gnu dot org
2005-11-05 10:48 ` steven at gcc dot gnu dot org
2005-12-15 6:50 ` [Bug rtl-optimization/23453] [4.0/4.1/4.2 " steven at gcc dot gnu dot org
2005-12-20 10:48 ` steven at gcc dot gnu dot org
2005-12-20 10:59 ` belyshev at depni dot sinp dot msu dot ru
2005-12-20 16:11 ` steven at gcc dot gnu dot org
2005-08-18 7:30 [Bug target/23453] New: [4.0 4.1 regression] miscompilation of PARI/GP on x86 debian-gcc at lists dot debian dot org
2005-08-19 1:09 ` [Bug rtl-optimization/23453] [4.0/4.1 regression] miscompilation of PARI/GP on x86 with gcse after reload belyshev at depni dot sinp dot msu dot ru
2005-08-19 19:51 ` belyshev at depni dot sinp dot msu dot ru
2005-09-27 16:24 ` mmitchel at gcc dot gnu dot org
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=20051014113832.23863.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).