public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Aleksandar Rakic <Aleksandar.Rakic@Syrmia.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "richard.guenther@gmail.com" <richard.guenther@gmail.com>,
	"jeffreyalaw@gmail.com" <jeffreyalaw@gmail.com>,
	"rguenther@suse.de" <rguenther@suse.de>,
	"jakub@redhat.com" <jakub@redhat.com>,
	Djordje Todorovic <Djordje.Todorovic@syrmia.com>,
	Jovan Dmitrovic <Jovan.Dmitrovic@Syrmia.com>
Subject: [PING] Re: [PATCH 1/2] ivopts: Revert computation of address cost complexity
Date: Wed, 22 May 2024 12:57:34 +0000	[thread overview]
Message-ID: <VI1PR03MB462267895891634FD8CA994EFCEB2@VI1PR03MB4622.eurprd03.prod.outlook.com> (raw)

Hi!

I'd like to ping the following patch:

https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647966.html
  a patch for the computation of the complexity for the unsupported addressing modes in ivopts

  This patch should be a fix for the bug which is described on the following link:
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109429
  It modifies the order of the complexity calculation. By fixing the complexities, the
  candidate selection is also fixed, which leads to the smaller code size.


Thanks

	Aleksandar Rakić

             reply	other threads:[~2024-05-22 12:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 12:57 Aleksandar Rakic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-06-26 12:28 Aleksandar Rakic
2024-06-26 12:50 ` Richard Biener
2024-06-26 14:18   ` Aleksandar Rakic
2024-04-11 15:09 Aleksandar Rakic
2024-04-02 10:42 Aleksandar Rakic
2024-03-18 20:27 Aleksandar Rakic
2024-03-27 11:21 ` [PING] " Aleksandar Rakic
2023-03-23 10:07 Jovan Dmitrovic

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=VI1PR03MB462267895891634FD8CA994EFCEB2@VI1PR03MB4622.eurprd03.prod.outlook.com \
    --to=aleksandar.rakic@syrmia.com \
    --cc=Djordje.Todorovic@syrmia.com \
    --cc=Jovan.Dmitrovic@Syrmia.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jeffreyalaw@gmail.com \
    --cc=rguenther@suse.de \
    --cc=richard.guenther@gmail.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).