public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/20134] [4.0 Regression] combine messes up subreg/zero_extend/compare/lshift Date: Wed, 23 Feb 2005 01:11:00 -0000 [thread overview] Message-ID: <20050222181444.3190.qmail@sourceware.org> (raw) In-Reply-To: <20050222001243.20134.janis@gcc.gnu.org> ------- Additional Comments From jakub at gcc dot gnu dot org 2005-02-22 18:14 ------- The testcase is indeed invalid. K&R definition can't serve as a prototype and whether a 32-bit argument is on PPC64 sign or zero extended to 64-bit depends on whether the argument is signed or unsigned. So, either prototypes must be used, or the caller must match the type of the arguments. if (exact_log2_wide (0x80000000) != 31) abort (); or if (exact_log2_wide ((unsigned int) -2147483648) != 31) abort (); work just fine. On many 64-bit arches this testcase will work anyway, as arguments are e.g. always sign extended to 64-bit (I believe Alpha is an example here) or zero extended to 64-bit. -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Keywords|wrong-code | Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20134
prev parent reply other threads:[~2005-02-22 18:14 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-22 7:46 [Bug tree-optimization/20134] New: 176.gcc miscompare with -m64 after DOM change janis at gcc dot gnu dot org 2005-02-22 7:51 ` [Bug tree-optimization/20134] " janis at gcc dot gnu dot org 2005-02-22 8:02 ` [Bug tree-optimization/20134] New: " Daniel Berlin 2005-02-22 8:07 ` [Bug tree-optimization/20134] " dberlin at dberlin dot org 2005-02-22 8:54 ` [Bug tree-optimization/20134] [4.0 Regression] " pinskia at gcc dot gnu dot org 2005-02-22 9:32 ` [Bug rtl-optimization/20134] " pinskia at gcc dot gnu dot org 2005-02-22 9:47 ` [Bug tree-optimization/20134] " janis at gcc dot gnu dot org 2005-02-22 9:48 ` [Bug rtl-optimization/20134] " pinskia at gcc dot gnu dot org 2005-02-22 9:51 ` pinskia at gcc dot gnu dot org 2005-02-22 22:06 ` [Bug rtl-optimization/20134] [4.0 Regression] combine messes up subreg/zero_extend/compare/lshift jakub at gcc dot gnu dot org 2005-02-23 1:11 ` jakub 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=20050222181444.3190.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).