public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anton at mips dot complang dot tuwien dot ac dot at" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/31152] New: -(x>y) generates wrong code Date: Mon, 12 Mar 2007 17:36:00 -0000 [thread overview] Message-ID: <bug-31152-895@http.gcc.gnu.org/bugzilla/> (raw) The actual gcc version is gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) When compiled and run with this gcc version, using the command line gcc -O xxx.c && a.out the attached program outputs -1, whereas the correct output is 0. If I use gcc 3.3.6 or leave away the -O flag, the program produces correct output. -- Summary: -(x>y) generates wrong code Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: anton at mips dot complang dot tuwien dot ac dot at GCC host triplet: arm-linux-gnu GCC target triplet: arm-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31152
next reply other threads:[~2007-03-12 17:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-12 17:36 anton at mips dot complang dot tuwien dot ac dot at [this message] 2007-03-12 17:43 ` [Bug tree-optimization/31152] " anton at mips dot complang dot tuwien dot ac dot at 2007-03-13 10:20 ` [Bug target/31152] " rguenth at gcc dot gnu dot org 2007-03-23 21:28 ` fb at frank-buss dot de 2007-06-19 9:41 ` rearnsha at gcc dot gnu dot org 2007-06-23 18:07 ` rearnsha at gcc dot gnu dot org 2007-06-23 18:11 ` rearnsha at gcc dot gnu dot org 2007-06-23 19:07 ` tbm at cyrius dot com 2007-06-23 19:08 ` tbm at cyrius dot com
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-31152-895@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).