public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/19417] [3.3 only] return value of some functions not properly set (in r3) Date: Sat, 15 Jan 2005 00:40:00 -0000 [thread overview] Message-ID: <20050115004010.11684.qmail@sourceware.org> (raw) In-Reply-To: <20050112234624.19417.cort@fsmlabs.com> ------- Additional Comments From dje at gcc dot gnu dot org 2005-01-15 00:40 ------- The inlined asm rtl_a_set() does not list any outputs or clobbers, so it looks like the compiler safely can assume that the value is unchanged. I am not sure why the compiler can assume that the value is zero, but the asm definitely will confuse it about the status of the register. Showing the register as killed in the asm fixes the code generation. I am going to mark this as invalid. Please reopen if you can explain to me why GCC should behave well with an asm statement that kills the value in a register but only lists inputs to the data dependency and flow parts of the compiler. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19417
prev parent reply other threads:[~2005-01-15 0:40 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-12 23:46 [Bug c/19417] New: " cort at fsmlabs dot com 2005-01-12 23:48 ` [Bug c/19417] " cort at fsmlabs dot com 2005-01-12 23:48 ` cort at fsmlabs dot com 2005-01-12 23:49 ` cort at fsmlabs dot com 2005-01-12 23:49 ` cort at fsmlabs dot com 2005-01-12 23:51 ` cort at fsmlabs dot com 2005-01-13 0:02 ` pinskia at gcc dot gnu dot org 2005-01-13 0:38 ` [Bug middle-end/19417] " pinskia at gcc dot gnu dot org 2005-01-13 0:44 ` pinskia at gcc dot gnu dot org 2005-01-14 23:24 ` [Bug middle-end/19417] [3.3 only] " pinskia at gcc dot gnu dot org 2005-01-15 0:40 ` dje at gcc dot gnu dot org [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=20050115004010.11684.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).