On 16/03/2020 13:45, Martin Liška wrote:
Hello.
I noticed some emails reaching gcc-patc...@gcc.gnu.org use the following
quoting:
```
case UNGT_EXPR:
case UNGE_EXPR:
case UNEQ_EXPR:
+ case MEM_REF:
/* Binary operations evaluating both arguments (increment and
=09 decrement are binary internally in GCC). */
orig_op0 =3D op0 =3D TREE_OPERAND (expr, 0);
@@ -435,6 +436,14 @@ c_fully_fold_internal (tree expr, bool i
=09 || TREE_CODE (TREE_TYPE (orig_op0)) =3D=3D FIXED_POINT_TYPE)
=09 && TREE_CODE (TREE_TYPE (orig_op1)) =3D=3D INTEGER_TYPE)
=09warn_for_div_by_zero (loc, op1);
+ if (code =3D=3D MEM_REF
+=09 && ret !=3D expr
+=09 && TREE_CODE (ret) =3D=3D MEM_REF)
+=09{
+=09 TREE_READONLY (ret) =3D TREE_READONLY (expr);
+=09 TREE_SIDE_EFFECTS (ret) =3D TREE_SIDE_EFFECTS (expr);
+=09 TREE_THIS_VOLATILE (ret) =3D TREE_THIS_VOLATILE (expr);
+=09}
```
It's probably related to the following email tag:
Content-Transfer-Encoding: quoted-printable
The format is problematic when copying a patch.
Email example:
https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542053.html
Thank you,
Martin
This isn't new. It's usually the sender that controls that, though it's
often automatic in their email client.
R.
