public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/42575] arm-eabi-gcc 64-bit multiply weirdness Date: Mon, 22 Feb 2010 21:06:00 -0000 [thread overview] Message-ID: <20100222210627.9075.qmail@sourceware.org> (raw) In-Reply-To: <bug-42575-17572@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from drow at gcc dot gnu dot org 2010-02-22 21:06 ------- (In reply to comment #3) > * What is the purpose of insn 12 here? It looks to me like this is dead code, > since r5 is restored in insn 38 (although, not knowing ARM so well, I may be > wrong). I couldn't figure this out either. Where did it come from - was it so late that we never DCE'd it, or does something bizarre claim to be dependent on the value? > Note how the sched1 pass has switched the two insns around. The register > allocator now decides to use two new registers here, because r0 and r3 are both > live. After RA, sched2 switches insn 9 and insn 10 again, and r2 and r3 become > available in insn 10 -- but this is too late. > > Question for the ARM maintainer now is: Why does sched1 want to swap insns 9 > and 10, when sched2 wants to swap them back again? I'm guessing, but presumably we want to separate the mul from the mla because they're dependent; the umull isn't. But I don't know what would swap them back again and that's probably the crux. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42575
next prev parent reply other threads:[~2010-02-22 21:06 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-01 17:33 [Bug c/42575] New: arm-eabi-gcc 4.2.1 " sliao at google dot com 2010-01-01 17:40 ` [Bug target/42575] " rguenth at gcc dot gnu dot org 2010-01-04 10:54 ` [Bug rtl-optimization/42575] arm-eabi-gcc " ramana at gcc dot gnu dot org 2010-02-08 10:47 ` steven at gcc dot gnu dot org 2010-02-08 10:52 ` steven at gcc dot gnu dot org 2010-02-22 21:06 ` drow at gcc dot gnu dot org [this message] 2010-07-29 12:40 ` bernds at gcc dot gnu dot org 2010-08-18 10:34 ` mkuvyrkov at gcc dot gnu dot org 2010-08-18 10:43 ` mkuvyrkov at gcc dot gnu dot org [not found] <bug-42575-4@http.gcc.gnu.org/bugzilla/> 2011-09-20 20:54 ` jules at gcc dot gnu.org 2013-05-29 9:55 ` ktkachov at gcc dot gnu.org 2014-02-14 7:44 ` bernd.edlinger at hotmail dot de 2014-02-14 7:47 ` bernd.edlinger at hotmail dot de 2014-11-17 16:23 ` ktkachov at gcc dot gnu.org 2015-02-12 14:40 ` ktkachov at gcc dot gnu.org 2015-03-26 16:14 ` ktkachov 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=20100222210627.9075.qmail@sourceware.org \ --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).