public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/63906] New: [5 Regression] lra_remat mis-compiles glibc on aarch64 Date: Mon, 17 Nov 2014 03:22:00 -0000 [thread overview] Message-ID: <bug-63906-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63906 Bug ID: 63906 Summary: [5 Regression] lra_remat mis-compiles glibc on aarch64 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: blocker Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target: aarch64-linux-gnu I don't have much information yet but I wanted to file this so I don't lose track of it. With lra_remat turned on, we get a crash inside dl_main. 0x000000400080386c <dl_main+5604>: ldr x2, [x3,w0,uxtw #3] => 0x0000004000803870 <dl_main+5608>: ldrb w1, [x2,#788] (gdb) p $x2 $1 = 0
next reply other threads:[~2014-11-17 3:22 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-17 3:22 pinskia at gcc dot gnu.org [this message] 2014-11-17 3:22 ` [Bug rtl-optimization/63906] " pinskia at gcc dot gnu.org 2014-11-17 3:53 ` pinskia at gcc dot gnu.org 2014-11-17 3:54 ` pinskia at gcc dot gnu.org 2014-11-17 4:46 ` [Bug rtl-optimization/63906] [5 Regression] dse after reload miscompiles glibc with lra_remat turned " pinskia at gcc dot gnu.org 2014-11-17 4:47 ` pinskia at gcc dot gnu.org 2014-11-17 5:01 ` [Bug rtl-optimization/63906] [5 Regression] lra_remat miscompiles glibc " pinskia at gcc dot gnu.org 2014-11-17 9:19 ` rguenth at gcc dot gnu.org 2014-11-17 20:30 ` vmakarov at gcc dot gnu.org 2014-11-18 0:15 ` vmakarov at gcc dot gnu.org 2014-11-18 3:23 ` pinskia 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-63906-4@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).