From: Aleksandar Rakic <Aleksandar.Rakic@Syrmia.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Aleksandar Rakic <Aleksandar.Rakic@Syrmia.com>
Subject: [PING] Re: [PATCH 1/2] ivopts: Revert computation of address cost complexity.
Date: Thu, 11 Apr 2024 15:09:56 +0000 [thread overview]
Message-ID: <VI1PR03MB462223D5E7EB9AB853E6D6C7FC052@VI1PR03MB4622.eurprd03.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
PING: I remind you that the patch for the computation of complexity for unsupported addressing modes ( https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109429 ) has been sent:
https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647966.html
next reply other threads:[~2024-04-11 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 15:09 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-05-22 12:57 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=VI1PR03MB462223D5E7EB9AB853E6D6C7FC052@VI1PR03MB4622.eurprd03.prod.outlook.com \
--to=aleksandar.rakic@syrmia.com \
--cc=gcc-patches@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).