From: Gaius Mulley <gaiusmod2@gmail.com>
To: Bernhard Reutner-Fischer via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
Subject: Re: [PATCH 05/14] m2: use _P() defines from tree.h
Date: Sun, 14 May 2023 02:44:14 +0100 [thread overview]
Message-ID: <87lehry9e9.fsf@debian> (raw)
In-Reply-To: <20230513232321.279733-6-rep.dot.nop@gmail.com> (Bernhard Reutner-Fischer via Gcc-patches's message of "Sun, 14 May 2023 01:23:12 +0200")
Bernhard Reutner-Fischer via Gcc-patches <gcc-patches@gcc.gnu.org>
writes:
> From: Bernhard Reutner-Fischer <aldot@gcc.gnu.org>
>
> gcc/m2/ChangeLog:
>
> * gm2-gcc/m2builtins.cc (doradix): Use _P defines from tree.h.
> (doplaces): Ditto.
> (doexponentmin): Ditto.
> (doexponentmax): Ditto.
> (dolarge): Ditto.
> (dosmall): Ditto.
> (dogUnderflow): Ditto.
> * gm2-gcc/m2convert.cc (unsafe_conversion_p): Ditto.
> * gm2-gcc/m2expr.cc (m2expr_build_unary_op_check): Ditto.
> (m2expr_build_binary_op_check): Ditto.
> * gm2-gcc/m2tree.cc (m2tree_is_var): Ditto.
> * gm2-gcc/m2treelib.cc (build_modify_expr): Ditto.
> * gm2-gcc/m2type.cc (gm2_finish_decl): Ditto.
> * m2pp.cc (hextree): Ditto.
> (m2pp_call_expr): Ditto.
Hi Bernhard,
from the m2 perspective - all looks good to me - thanks for the patch,
regards,
Gaius
next prev parent reply other threads:[~2023-05-14 1:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 23:23 [PATCH 00/14] " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 01/14] ada: " Bernhard Reutner-Fischer
2023-05-14 23:03 ` Jeff Law
2023-05-18 19:59 ` Bernhard Reutner-Fischer
2023-05-15 10:05 ` Eric Botcazou
2023-05-18 19:53 ` Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 02/14] analyzer: " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 03/14] gcc/config/*: " Bernhard Reutner-Fischer
2023-05-14 8:21 ` Iain Sandoe
2023-05-15 7:46 ` Richard Biener
2023-05-13 23:23 ` [PATCH 04/14] c++: " Bernhard Reutner-Fischer
2023-06-01 15:24 ` Patrick Palka
2023-06-01 16:33 ` Bernhard Reutner-Fischer
2023-06-01 18:10 ` Bernhard Reutner-Fischer
2023-08-02 16:51 ` Patrick Palka
2023-08-08 20:31 ` Jason Merrill
2023-11-15 17:42 ` Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 05/14] m2: " Bernhard Reutner-Fischer
2023-05-14 1:44 ` Gaius Mulley [this message]
2023-05-14 1:47 ` Gaius Mulley
2023-05-13 23:23 ` [PATCH 06/14] lto: " Bernhard Reutner-Fischer
2023-05-15 7:45 ` Richard Biener
2023-05-13 23:23 ` [PATCH 07/14] d: " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 08/14] fortran: " Bernhard Reutner-Fischer
2023-05-14 13:10 ` Mikael Morin
2023-05-18 15:18 ` Bernhard Reutner-Fischer
2023-05-18 19:20 ` Mikael Morin
2023-05-19 19:19 ` Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 09/14] rust: " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 10/14] c: " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 11/14] objc: " Bernhard Reutner-Fischer
2023-05-14 8:13 ` Iain Sandoe
2023-05-13 23:23 ` [PATCH 12/14] go: " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 13/14] omp: " Bernhard Reutner-Fischer
2023-05-13 23:23 ` [PATCH 14/14] gcc: " Bernhard Reutner-Fischer
2023-05-15 7:45 ` 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=87lehry9e9.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=aldot@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
/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).