public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jseward at acm dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/98692] Unitialized Values reported only with -Os Date: Wed, 10 Feb 2021 14:53:54 +0000 [thread overview] Message-ID: <bug-98692-4-TzXNP27mWw@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98692-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98692 --- Comment #22 from jseward at acm dot org --- Looking back at the above, it's now clearer what the problem is: # Park potentially live data in the red zone _savegpr0_14: std r14,-144(r1) _savegpr0_15: std r15,-136(r1) _savegpr0_16: std r16,-128(r1) _savegpr0_17: std r17,-120(r1) _savegpr0_18: std r18,-112(r1) _savegpr0_19: std r19,-104(r1) _savegpr0_20: std r20,-96(r1) _savegpr0_21: std r21,-88(r1) _savegpr0_22: std r22,-80(r1) _savegpr0_23: std r23,-72(r1) _savegpr0_24: std r24,-64(r1) _savegpr0_25: std r25,-56(r1) _savegpr0_26: std r26,-48(r1) _savegpr0_27: std r27,-40(r1) _savegpr0_28: std r28,-32(r1) _savegpr0_29: std r29,-24(r1) _savegpr0_30: std r30,-16(r1) _savegpr0_31: std r31,-8(r1) std r0, 16(r1) # And ka-zap! Memcheck paints -288(r1) .. -1(r1) as undefined. blr # So now they're all "unusable".
next prev parent reply other threads:[~2021-02-10 14:53 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 21:11 [Bug rtl-optimization/98692] New: " nick.child at ibm dot com 2021-01-14 21:11 ` [Bug rtl-optimization/98692] " nick.child at ibm dot com 2021-01-15 8:58 ` marxin at gcc dot gnu.org 2021-01-15 9:24 ` marxin at gcc dot gnu.org 2021-01-15 23:58 ` segher at gcc dot gnu.org 2021-01-16 0:01 ` segher at gcc dot gnu.org 2021-01-18 8:05 ` marxin at gcc dot gnu.org 2021-01-18 15:11 ` acsawdey at gcc dot gnu.org 2021-01-19 15:03 ` nick.child at ibm dot com 2021-02-08 21:29 ` willschm at gcc dot gnu.org 2021-02-08 21:40 ` mark at gcc dot gnu.org 2021-02-08 22:00 ` willschm at gcc dot gnu.org 2021-02-09 9:34 ` mark at gcc dot gnu.org 2021-02-09 9:44 ` mark at gcc dot gnu.org 2021-02-09 21:04 ` willschm at gcc dot gnu.org 2021-02-09 22:12 ` segher at gcc dot gnu.org 2021-02-09 22:21 ` segher at gcc dot gnu.org 2021-02-10 9:38 ` mark at gcc dot gnu.org 2021-02-10 14:09 ` mark at gcc dot gnu.org 2021-02-10 14:35 ` jseward at acm dot org 2021-02-10 14:44 ` jakub at gcc dot gnu.org 2021-02-10 14:51 ` jseward at acm dot org 2021-02-10 14:53 ` jseward at acm dot org [this message] 2021-02-10 16:31 ` segher at gcc dot gnu.org 2021-02-10 16:34 ` segher 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-98692-4-TzXNP27mWw@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).