From: Andreas Schwab <schwab@suse.de>
To: Andrew Cooper via Gcc <gcc@gcc.gnu.org>
Cc: Alexander Monakov <amonakov@ispras.ru>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Builtin for consulting value analysis (better ffs() code gen)
Date: Thu, 14 Mar 2024 13:03:45 +0100 [thread overview]
Message-ID: <mvm8r2lm34u.fsf@suse.de> (raw)
In-Reply-To: <a49dd682-c5bb-4674-a044-4720f4c0a059@citrix.com> (Andrew Cooper via Gcc's message of "Thu, 14 Mar 2024 11:30:12 +0000")
On Mär 14 2024, Andrew Cooper via Gcc wrote:
> so any known-constant value can be folded. What I'm dealing with is the
> remainder of the cases.
Which cases remain?
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-03-14 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 0:03 Andrew Cooper
2024-03-14 6:04 ` Alexander Monakov
2024-03-14 11:30 ` Andrew Cooper
2024-03-14 12:03 ` Andreas Schwab [this message]
2024-03-14 15:33 ` Andrew Cooper
2024-03-21 8:15 ` LIU Hao
2024-03-14 11:02 ` Florian Weimer
2024-03-14 11:52 ` Andrew Cooper
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=mvm8r2lm34u.fsf@suse.de \
--to=schwab@suse.de \
--cc=amonakov@ispras.ru \
--cc=andrew.cooper3@citrix.com \
--cc=gcc@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).