public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/109032] message 'compiler checks to force' is too complicated
Date: Sun, 05 Mar 2023 22:32:21 +0000 [thread overview]
Message-ID: <bug-109032-4-b189ltlsli@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109032-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
--- Comment #4 from Roland Illig <roland.illig at gmx dot de> ---
While here:
> (*
> BuildDivM2 - build and return ((op2 < 0) : (op1 divtrunc op2) ? (op1 divfloor op2))
> when -fiso, -fpim4 or -fpositive-mod-floor-div is present else
> return op1 div trunc op2
> *)
Did you swap the operators '?' and ':' here?
I had to look this up because this message was completely unclear to me:
> force positive result from MOD and DIV result floor
The explanation from gm2.texi is much clearer:
> All modulus results are positive and the results from the division are
rounded to the floor.
next prev parent reply other threads:[~2023-03-05 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 22:06 [Bug modula2/109032] New: " roland.illig at gmx dot de
2023-03-05 22:10 ` [Bug modula2/109032] " roland.illig at gmx dot de
2023-03-05 22:17 ` roland.illig at gmx dot de
2023-03-05 22:21 ` roland.illig at gmx dot de
2023-03-05 22:32 ` roland.illig at gmx dot de [this message]
2023-03-05 22:36 ` roland.illig at gmx dot de
2023-03-08 15:43 ` gaius at gcc dot gnu.org
2023-03-17 14:33 ` cvs-commit at gcc dot gnu.org
2023-03-17 14:34 ` gaius at gcc dot gnu.org
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=bug-109032-4-b189ltlsli@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).