public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/12837] New: The mod vpt does not work on PPC
Date: Thu, 30 Oct 2003 06:38:00 -0000	[thread overview]
Message-ID: <20031030063759.12837.pinskia@gcc.gnu.org> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12837

           Summary: The mod vpt does not work on PPC
           Product: gcc
           Version: 3.4
            Status: UNCONFIRMED
          Keywords: pessimizes-code, patch
          Severity: enhancement
          Priority: P2
         Component: optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
GCC target triplet: powerpc-*-*

This is to keep track of two patches: <http://gcc.gnu.org/ml/gcc-patches/2003-10/
msg02412.html> and <http://gcc.gnu.org/ml/gcc-patches/2003-10/msg02414.html> which 
have the mod Value based feeedback work on PPC and other targets that do not have a MOD or an 
UMOD rtl.  Note I will fix up the first patch to use find_reg_equiv_note instead.


             reply	other threads:[~2003-10-30  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30  6:38 pinskia at gcc dot gnu dot org [this message]
2003-10-30  6:40 ` [Bug optimization/12837] " pinskia at gcc dot gnu dot org
2004-02-08  6:45 ` pinskia at gcc dot gnu dot org
2004-02-14 21:12 ` pinskia at gcc dot gnu dot org
2004-04-05  0:51 ` pinskia at gcc dot gnu dot org
2004-05-26 11:43 ` [Bug rtl-optimization/12837] " pinskia at gcc dot gnu dot org
2005-04-06 18:26 ` pinskia 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=20031030063759.12837.pinskia@gcc.gnu.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).