public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@porcupine.slc.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/7250: __ashrdi3 returns wrong value on 32 bit hppa Date: Tue, 09 Jul 2002 15:56:00 -0000 [thread overview] Message-ID: <20020709225601.19780.qmail@sources.redhat.com> (raw) The following reply was made to PR target/7250; it has been noted by GNATS. From: Jeff Law <law@porcupine.slc.redhat.com> To: sje@cup.hp.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/7250: __ashrdi3 returns wrong value on 32 bit hppa Date: Tue, 09 Jul 2002 16:48:46 -0600 In message <20020709203142.10159.qmail@sources.redhat.com>, sje@cup.hp.com writ es: > >>Number: 7250 >>Category: target >>Synopsis: __ashrdi3 returns wrong value on 32 bit hppa >>Confidential: no >>Severity: serious >>Priority: medium >>Responsible: unassigned >>State: open >>Class: sw-bug >>Submitter-Id: net >>Arrival-Date: Tue Jul 09 13:36:01 PDT 2002 >>Closed-Date: >>Last-Modified: >>Originator: sje@cup.hp.com >>Release: 3.0.2 >>Organization: >>Environment: >hppa1.1-hp-hpux11.00 >>Description: >Arithmatic right shift of long long (64 bit) value returns wrong value. See >attached file (x.c) for a program that >fails with -O0 (with call to __ashrdi3) but works with optimization because t >he call is optimized away. > >>How-To-Repeat: >Compile x.c and run it *without* optimization on a 32 bit PA machine. With o >ptimization it works. Can you look a little deeper into this? It seems quite odd that ashrdi3 would return the wrong value for a shift count of zero as it special cases zero count in libgcc2.c: DWtype __ashrdi3 (DWtype u, word_type b) { DWunion w; word_type bm; DWunion uu; if (b == 0) return u; [ ... ] Jeff
next reply other threads:[~2002-07-09 22:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-09 15:56 Jeff Law [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-07-10 11:56 Jeff Law 2002-07-10 11:47 law 2002-07-09 16:16 Steve Ellcey 2002-07-09 13:36 sje
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=20020709225601.19780.qmail@sources.redhat.com \ --to=law@porcupine.slc.redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).