From: Graham Stott <graham.stott@btinternet.com>
To: Vladimir Makarov <vmakarov@redhat.com>, Jeff Law <law@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: patch to fix PR 48435
Date: Fri, 08 Apr 2011 17:28:00 -0000 [thread overview]
Message-ID: <737654.9385.qm@web87112.mail.ird.yahoo.com> (raw)
In-Reply-To: <4D9F272B.5090308@redhat.com>
Vladimir,
The wrong PR 4435 was in referrenced the commit
--- On Fri, 8/4/11, Jeff Law <law@redhat.com> wrote:
> From: Jeff Law <law@redhat.com>
> Subject: Re: patch to fix PR 48435
> To: "Vladimir Makarov" <vmakarov@redhat.com>
> Cc: "gcc-patches" <gcc-patches@gcc.gnu.org>
> Date: Friday, 8 April, 2011, 16:18
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 04/07/11 13:41, Vladimir Makarov wrote:
> > The following patch should solve problem
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48435.
> It might solve other
> > latest IRA problems too including performance related
> ones. The patch
> > is for targets which require some values to be placed
> in hard registers
> > starting with an even (odd) hard registers.
> >
> > I already addressed an analogous problem recently and
> the patch I sent
> > that time although solved some problems it created
> even more new
> > problems. I should acknowledge this.
> >
> > The problem was in that profitable hard regs were used
> for colorability
> > criterion and finding hard registers where allocno
> values can be resided
> > but *also* as starting allocno hard registers.
> It resulted in spilling
> > allocnos which should be placed in multi-registers
> starting on a
> > specific border because profitable hard registers were
> only starting
> > registers and when we calculated number of available
> hard registers
> > multi-register allocnos can not fit only in their
> starting hard registers.
> >
> > The following patch was successfully bootstrapped on
> x86/x86-64 and on
> > i686 with H.J.'s autotester options.
> >
> > OK to commit?
> >
> > 2011-04-07 Vladimir Makarov <vmakarov@redhat.com>
> >
> > PR 4435
> > * ira-color.c
> (setup_profitable_hard_regs): Add comments.
> > Don't take prohibited hard
> regs into account.
> >
> (setup_conflict_profitable_regs): Rename
> to
> > get_conflict_profitable_regs.
> > (check_hard_reg_p): Check
> prohibited hard regs.
> OK.
> jeff
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJNnycrAAoJEBRtltQi2kC70DsH/A7fnYlawxDvYPeULGb1ctQD
> 6LYWBWhJY4UDTiUNjLEzwALpq2XccVzubz1KEMI3wOndIHHYM2ykbsgTqCKmXqhf
> ZthBjzNUtE/i7jSxK8JK3SEShqs2j7vaAvlkUKbdF7O61rhQap8MRnD2umHfrbet
> PFea7MedpaC96mazzoyUWlzwWCt2CQhOlMFGlC44bxB1FrKy0nUjeIM7kWqjqG5W
> Y9lV8RlC4O2cLST5qHpqtssLSO4omPlKsEUBEKW4E/87UCoFAxP0n8NOZ1EFgMsc
> 3SlhSv+Dpinfh79gjHXt5+CH33bXTecf8Jfyd89Rn6huzL9OhAXJy+MjMi6cBm0=
> =KSaH
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2011-04-08 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 19:41 Vladimir Makarov
2011-04-08 15:18 ` Jeff Law
2011-04-08 17:28 ` Graham Stott [this message]
2011-04-08 17:50 ` Vladimir Makarov
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=737654.9385.qm@web87112.mail.ird.yahoo.com \
--to=graham.stott@btinternet.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=vmakarov@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).