panders in an unexpected way', should I put the optimization
in another place and try to deal with the zero sign or is it fine the
way it is?
Rafael Tsuha
Em ter, 10 de set de 2019 às 12:23, Jeff Law escreveu:
>
> On 9/10/19 1:36 AM, Uros Bizjak wrote:
> > On Mon, Sep 9, 2019 at 8:44
Hi, Jeff
Em seg, 29 de abr de 2019 às 18:22, Jeff Law escreveu:
>
> On 1/22/19 12:31 PM, Rafael Tsuha wrote:
> > This patch simplifies the expression sinh (x) / cosh (x) to tanh (x).
> > This rule is mathematically valid.
> >
> > There's a slight differen
ping
Em sex, 24 de mai de 2019 às 09:53, Rafael Tsuha escreveu:
>
> This patch adds a function to warn when there's a bitwise operation
> between a boolean and any other type. This kind of operation is
> probably a programmer mistake that may lead to unexpected behavior
> b
gcc/c-family/ChangeLog
2019-05-24 Rafael Tsuha
* c-warn.c (warn_logical_operator): Check for missplaced bitwise op.
gcc/testsuite/ChangeLog
2019-05-24 Rafael Tsuha
PR c/17896
* gcc.dg/boolean-bitwise.c: New test.
Index: gcc/c-family/c-w
without the
optimization, the result is +0.
When running the testsuite, the test gfortran.dg/pr79966.f90 failed,
but it seems unrelated to this patch
My architecture is x86_64.
gcc/ChangeLog
2019-01-22 Rafael Tsuha
* match.pd (sinh (x) / cosh (x)): New simplification rule.
gcc/testsuit
