public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/103432] [12 regression] libjxl-0.5 is miscompiled, works fine with -fno-ipa-modref Date: Fri, 26 Nov 2021 00:31:16 +0000 [thread overview] Message-ID: <bug-103432-4-m9oNtCmSQt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103432-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103432 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Target Milestone|12.0 |--- Keywords|wrong-code | Known to work|11.2.0 | Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2021-11-26 Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org CC| |hubicka at gcc dot gnu.org Component|ipa |tree-optimization --- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> --- It fails with ./xgcc -B ./ -O2 d.ii -fdbg-cnt=ipa_mod_ref_pta:189 -fdump-tree-all-details -fdump-ipa-all-details and works ./xgcc -B ./ -O2 d.ii -fdbg-cnt=ipa_mod_ref_pta:188 -fdump-tree-all-details -fdump-ipa-all-details The difference in optimized dump is: int main () { struct DCTFrom D.11418; @@ -2805,12 +2810,7 @@ float x[4]; struct DCTTo D.11356; struct DCTFrom D.11355; - float _3; - float _4; - double _6; struct FILE * stderr.3_8; - double _9; - struct FILE * stderr.4_11; float _12; float _13; double _15; @@ -2996,30 +2996,10 @@ {anonymous}::IDCT1DWrapper.constprop<4, 1, {anonymous}::DCTFrom, {anonymous}::DCTTo> (&D.11400, &D.11356); D.11400 ={v} {CLOBBER}; D.11356 ={v} {CLOBBER}; - _3 = out[2]; - _4 = _3 - 1.0e+0; - actual_accuracy_5 = ABS_EXPR <_4>; - if (actual_accuracy_5 > 9.999999974752427078783512115478515625e-7) - goto <bb 11>; [0.04%] - else - goto <bb 12>; [99.96%] - - <bb 11> [local count: 429325]: - _6 = (double) actual_accuracy_5; stderr.3_8 = stderr; - fprintf (stderr.3_8, "ERROR: Too low accuracy: exp=%f act=%f\n", 9.999999974752427078783512115478515625e-7, _6); + fprintf (stderr.3_8, "ERROR: Too low accuracy: exp=%f act=%f\n", 9.999999974752427078783512115478515625e-7, 1.0e+0); exit (1); - <bb 12> [local count: 1072883004]: - _9 = (double) actual_accuracy_5; - stderr.4_11 = stderr; - fprintf (stderr.4_11, "OK: Good accuracy: exp=%f act=%f\n", 9.999999974752427078783512115478515625e-7, _9); - x ={v} {CLOBBER}; - out ={v} {CLOBBER}; - coeffs ={v} {CLOBBER}; - scratch_space ={v} {CLOBBER}; - return 0; - } And I suppose we are not expected to optimize out the "Good accuracy" message :) So it looks out is modified by {anonymous}::IDCT1DWrapper.constprop<4, 1, {anonymous}::DCTFrom, {anonymous}::DCTTo> (&D.11400, &D.11356); but for some reason ipa propagation gets no_indirect_clobber for param1. This seems wrong since to->data is written to, so it is an indirect clobber. I may be able to look more into this only tomorrow - it is bit late.
next prev parent reply other threads:[~2021-11-26 0:31 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-25 23:59 [Bug tree-optimization/103432] New: " slyfox at gcc dot gnu.org 2021-11-26 0:19 ` [Bug ipa/103432] " pinskia at gcc dot gnu.org 2021-11-26 0:31 ` hubicka at gcc dot gnu.org [this message] 2021-11-26 0:33 ` pinskia at gcc dot gnu.org 2021-11-26 0:36 ` pinskia at gcc dot gnu.org 2021-11-26 7:24 ` rguenth at gcc dot gnu.org 2021-11-26 9:14 ` hubicka at kam dot mff.cuni.cz 2021-11-26 12:46 ` [Bug ipa/103432] [11 " hubicka at gcc dot gnu.org 2021-11-26 12:47 ` marxin at gcc dot gnu.org 2021-11-26 13:53 ` rguenth at gcc dot gnu.org 2021-11-26 22:45 ` slyfox at gcc dot gnu.org 2022-04-07 12:04 ` cvs-commit at gcc dot gnu.org 2022-04-07 12:05 ` rguenth 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-103432-4-m9oNtCmSQt@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).