* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated roland.illig at gmx dot de
@ 2023-03-05 22:10 ` roland.illig at gmx dot de
2023-03-05 22:17 ` roland.illig at gmx dot de
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: roland.illig at gmx dot de @ 2023-03-05 22:10 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
--- Comment #1 from Roland Illig <roland.illig at gmx dot de> ---
While here:
> turns on runtime checking to check whether a CASE statement requires an ELSE clause when on was not specified
Did you mean "when one was not"?
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated 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
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: roland.illig at gmx dot de @ 2023-03-05 22:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
--- Comment #2 from Roland Illig <roland.illig at gmx dot de> ---
While here:
> turns on runtime checking to check whether a floating point number is about to exceed range
What exactly does "is about to" mean, and why didn't you just write "exceeds
the range"?
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated 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
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: roland.illig at gmx dot de @ 2023-03-05 22:21 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
--- Comment #3 from Roland Illig <roland.illig at gmx dot de> ---
While here:
> specify the library order, currently legal entries include: log, min, pim, iso or their directory name equivalent m2log, m2min, m2pim, m2iso.
In what legislation are these entries "legal"?
Why the word 'include'? That means that there are others that are not listed
here.
This message ends with a '.', the other messages don't.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated roland.illig at gmx dot de
` (2 preceding siblings ...)
2023-03-05 22:21 ` roland.illig at gmx dot de
@ 2023-03-05 22:32 ` roland.illig at gmx dot de
2023-03-05 22:36 ` roland.illig at gmx dot de
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: roland.illig at gmx dot de @ 2023-03-05 22:32 UTC (permalink / raw)
To: gcc-bugs
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.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated roland.illig at gmx dot de
` (3 preceding siblings ...)
2023-03-05 22:32 ` roland.illig at gmx dot de
@ 2023-03-05 22:36 ` roland.illig at gmx dot de
2023-03-08 15:43 ` gaius at gcc dot gnu.org
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: roland.illig at gmx dot de @ 2023-03-05 22:36 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
--- Comment #5 from Roland Illig <roland.illig at gmx dot de> ---
While here:
> dependancies
Typo; should be dependencies.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated roland.illig at gmx dot de
` (4 preceding siblings ...)
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
7 siblings, 0 replies; 9+ messages in thread
From: gaius at gcc dot gnu.org @ 2023-03-08 15:43 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
Gaius Mulley <gaius at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0 |1
Last reconfirmed| |2023-03-08
--- Comment #6 from Gaius Mulley <gaius at gcc dot gnu.org> ---
Many thanks for reporting these areas of poor error messages - I'll change all
of these.
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated roland.illig at gmx dot de
` (5 preceding siblings ...)
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
7 siblings, 0 replies; 9+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-03-17 14:33 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Gaius Mulley <gaius@gcc.gnu.org>:
https://gcc.gnu.org/g:6bfb5eae96b65894da1301e966568fdf32bf64d0
commit r13-6737-g6bfb5eae96b65894da1301e966568fdf32bf64d0
Author: Gaius Mulley <gaiusmod2@gmail.com>
Date: Fri Mar 17 14:32:22 2023 +0000
PR modula2/109032 - message 'compiler checks to force' is too complicated
Correct typos and improve the descriptions of command line options.
Improve comments in gm2-gcc/m2expr.cc.
gcc/m2/ChangeLog:
PR modula2/109032
* gm2-gcc/m2expr.cc: Correct ? : order in comments.
(m2expr_BuildDivM2): Improve comment.
* lang.opt: Improve option descriptions.
Signed-off-by: Gaius Mulley <gaiusmod2@gmail.com>
^ permalink raw reply [flat|nested] 9+ messages in thread* [Bug modula2/109032] message 'compiler checks to force' is too complicated
2023-03-05 22:06 [Bug modula2/109032] New: message 'compiler checks to force' is too complicated roland.illig at gmx dot de
` (6 preceding siblings ...)
2023-03-17 14:33 ` cvs-commit at gcc dot gnu.org
@ 2023-03-17 14:34 ` gaius at gcc dot gnu.org
7 siblings, 0 replies; 9+ messages in thread
From: gaius at gcc dot gnu.org @ 2023-03-17 14:34 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109032
Gaius Mulley <gaius at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Gaius Mulley <gaius at gcc dot gnu.org> ---
Thanks for reporting - now closing as the patch has been applied.
^ permalink raw reply [flat|nested] 9+ messages in thread