From: Richard Biener <richard.guenther@gmail.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: Andrew MacLeod <amacleod@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH] Add divide by zero side effect.
Date: Fri, 20 May 2022 10:04:29 +0200 [thread overview]
Message-ID: <CAFiYyc3Rf4WpamDiw9xrNn8Hb6hTVU9jAB40EpXsmgyFJdsYXg@mail.gmail.com> (raw)
In-Reply-To: <18d5bea-e46c-e2f5-1495-ab55ddff6c47@ispras.ru>
On Fri, May 20, 2022 at 8:38 AM Alexander Monakov <amonakov@ispras.ru> wrote:
>
> On Fri, 20 May 2022, Richard Biener via Gcc-patches wrote:
>
> > > Still waiting for a suggestion, since "side effect" is the description
> > > that made sense to me :-)
> >
> > I think side-effect captures it quite well even if it overlaps with a term
> > used in language standards. Doing c = a << b has the side-effect on
> > imposing a range on 'b' rather than just affecting 'c' (and its range).
> > You could call it 'alternate effect' but that sounds just awkward ;)
>
> I suggest 'deduce', 'deduction', 'deducing a range'. What the code is actually
> doing is deducing that 'b' in 'a / b' cannot be zero. Function in GCC might be
> called like 'deduce_ranges_from_stmt'.
So how would you call determining the range of 'c' from the ranges of
'a' and 'b',
isn't that 'deduction' as well?
> Please don't overload 'side effect' if possible.
>
> Alexander
next prev parent reply other threads:[~2022-05-20 8:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 18:39 Andrew MacLeod
2022-05-18 6:28 ` Richard Biener
2022-05-18 13:20 ` Andrew MacLeod
2022-05-18 18:13 ` Segher Boessenkool
2022-05-18 20:24 ` Andrew MacLeod
2022-05-18 20:40 ` Segher Boessenkool
2022-05-19 13:22 ` Andrew MacLeod
2022-05-19 22:23 ` Segher Boessenkool
2022-05-20 2:14 ` Andrew MacLeod
2022-05-20 6:25 ` Richard Biener
2022-05-20 6:38 ` Alexander Monakov
2022-05-20 8:04 ` Richard Biener [this message]
2022-05-20 8:17 ` Alexander Monakov
2022-05-20 11:49 ` Richard Biener
2022-05-22 18:55 ` Alexander Monakov
2022-05-20 8:11 ` Eric Botcazou
2022-05-20 14:39 ` Segher Boessenkool
2022-05-20 19:18 ` Bernhard Reutner-Fischer
2022-05-25 14:35 ` [COMMITTED] Use infer instead of side-effect for ranges Andrew MacLeod
2022-05-25 16:29 ` Segher Boessenkool
2022-05-20 8:13 ` [PATCH] Add divide by zero side effect Eric Botcazou
2022-05-20 12:09 ` Alexandre Oliva
2022-05-27 19:33 ` Andi Kleen
2022-05-27 19:56 ` Andrew MacLeod
2022-05-28 11:52 ` Eric Gallager
2022-05-30 12:24 ` Richard Biener
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=CAFiYyc3Rf4WpamDiw9xrNn8Hb6hTVU9jAB40EpXsmgyFJdsYXg@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=amacleod@redhat.com \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).