public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/104675] [9/10/11/12 Regression] ICE: in expand_expr_real_2, at expr.cc:9773 at -O with __real__ + __imag__ extraction Date: Thu, 24 Feb 2022 10:52:50 +0000 [thread overview] Message-ID: <bug-104675-4-CMdwj25p32@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104675-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104675 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|10.3.1, 11.2.1, 12.0, | |6.5.0, 7.5.0, 8.5.0, 9.4.1 | --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- It isn't just that match.pd change though, consider: _Complex int foo (_Complex int a) { return (-1 + -1i) - a; } _Complex int bar (_Complex int a) { return - a - (1 + 1i); } _Complex int baz (_Complex int a) { _Complex int b = -1 + -1i; return b - a; } _Complex int qux (_Complex int a) { _Complex int b = 1 + 1i; return - a - b; } I think both: /* -A - 1 -> ~A */ (simplify (minus (convert? (negate @0)) integer_each_onep) (if (!TYPE_OVERFLOW_TRAPS (type) && tree_nop_conversion_p (type, TREE_TYPE (@0))) (bit_not (convert @0)))) /* -1 - A -> ~A */ (simplify (minus integer_all_onesp @0) (bit_not @0)) needs to punt for COMPLEX_TYPE.
next prev parent reply other threads:[~2022-02-24 10:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-24 10:24 [Bug rtl-optimization/104675] New: " zsojka at seznam dot cz 2022-02-24 10:29 ` [Bug rtl-optimization/104675] " jakub at gcc dot gnu.org 2022-02-24 10:32 ` pinskia at gcc dot gnu.org 2022-02-24 10:52 ` jakub at gcc dot gnu.org [this message] 2022-02-24 11:00 ` [Bug tree-optimization/104675] " pinskia at gcc dot gnu.org 2022-02-24 11:13 ` jakub at gcc dot gnu.org 2022-02-24 14:28 ` glisse at gcc dot gnu.org 2022-02-25 9:56 ` cvs-commit at gcc dot gnu.org 2022-02-25 10:53 ` jakub at gcc dot gnu.org 2022-02-25 20:25 ` cvs-commit at gcc dot gnu.org 2022-02-25 20:27 ` [Bug tree-optimization/104675] [9/10/11 " jakub at gcc dot gnu.org 2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org 2022-03-29 5:53 ` cvs-commit at gcc dot gnu.org 2022-03-30 8:15 ` [Bug tree-optimization/104675] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-10 8:24 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:36 ` jakub 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-104675-4-CMdwj25p32@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: linkBe 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).