From: Richard Biener <richard.guenther@gmail.com>
To: Aleksandar Rakic <Aleksandar.Rakic@syrmia.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"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: Re: [PING] Re: [PATCH 1/2] ivopts: Revert computation of address cost complexity
Date: Wed, 26 Jun 2024 14:50:10 +0200 [thread overview]
Message-ID: <CAFiYyc0=_ZjCvoYvyfb4b_unZfp9f1HiAxm9-r0KxOfE3+s-1Q@mail.gmail.com> (raw)
In-Reply-To: <PA4PR03MB68644C9A3916D4B842E47E54FCD62@PA4PR03MB6864.eurprd03.prod.outlook.com>
On Wed, Jun 26, 2024 at 2:28 PM Aleksandar Rakic
<Aleksandar.Rakic@syrmia.com> wrote:
>
> 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
The thread starting at
https://sourceware.org/pipermail/gcc-patches/2022-October/604128.html
contains much information. The mail you point to contains
inappropriate testsuite additions,
refers to a commit that doesn't look relevant and in fact does not
"revert" anything. I also
can't remember seeing it, it might have been classified as spam.
I would consider to instead of citing the patch by reference to re-post it.
Richard.
> 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ć
next prev parent reply other threads:[~2024-06-26 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 12:28 Aleksandar Rakic
2024-06-26 12:50 ` Richard Biener [this message]
2024-06-26 14:18 ` Aleksandar Rakic
-- strict thread matches above, loose matches on Subject: below --
2024-05-22 12:57 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='CAFiYyc0=_ZjCvoYvyfb4b_unZfp9f1HiAxm9-r0KxOfE3+s-1Q@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=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 \
/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).