public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "NickParker at Eaton dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50281] result registers are overwritten giving incorrect result Date: Sun, 04 Sep 2011 21:22:00 -0000 [thread overview] Message-ID: <bug-50281-4-hZyvMEWeNS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50281-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50281 --- Comment #10 from NickParker at Eaton dot com 2011-09-04 21:22:30 UTC --- Richard, 'bogus' isnt a technical term I'm familiar with - I'm not entirely sure what you mean, however, I have found the problem with my ASM code. If you'll notice I am adding partial products to r4,r5,r6,r7 without them ever being initialised. What was missing was initialistion of the temporary result registers r4,r5,r6,r7 where I am generating my result. After adding these initialisatons, and also a few "movw's" for a few less cycles in a couple of places, the code now works correctly. Thanks for your input and sorry that I made a mess of reporting this bug, which was nothing to do with the compiler. Thanks, Nick.
prev parent reply other threads:[~2011-09-04 21:22 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-03 0:52 [Bug c/50281] New: " NickParker at Eaton dot com 2011-09-03 1:07 ` [Bug inline-asm/50281] " pinskia at gcc dot gnu.org 2011-09-03 1:09 ` [Bug c/50281] " NickParker at Eaton dot com 2011-09-03 1:11 ` [Bug target/50281] " pinskia at gcc dot gnu.org 2011-09-03 1:13 ` pinskia at gcc dot gnu.org 2011-09-03 1:29 ` NickParker at Eaton dot com 2011-09-03 1:30 ` NickParker at Eaton dot com 2011-09-03 1:32 ` NickParker at Eaton dot com 2011-09-03 1:39 ` pinskia at gcc dot gnu.org 2011-09-03 4:45 ` NickParker at Eaton dot com 2011-09-03 4:47 ` NickParker at Eaton dot com 2011-09-03 8:50 ` rguenth at gcc dot gnu.org 2011-09-04 21:22 ` NickParker at Eaton dot com [this message]
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-50281-4-hZyvMEWeNS@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).