public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pavenis@latnet.lv To: gcc-gnats@gcc.gnu.org Subject: optimization/4867: gcc-3.1 20011112 generates wrong code for integer division Date: Fri, 02 Nov 2001 07:21:00 -0000 [thread overview] Message-ID: <20011113171639.18597.qmail@sourceware.cygnus.com> (raw) >Number: 4867 >Category: optimization >Synopsis: gcc-3.1 20011112 generates wrong code for integer division >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Tue Nov 13 09:26:01 PST 2001 >Closed-Date: >Last-Modified: >Originator: Andris Pavenis >Release: gcc-3.1 20011112 (experimental), gcc-3.1 20011030 (experimental) >Organization: >Environment: gcc-3.1 20011112 for i686-pc-linux-gnu, gcc-3.1 20011030 for i586-pc-msdosdjgpp >Description: gcc-3.1 generates bad code for integer division and taking remainder when result is being stored in structure members which size is specified in bits (8 bits in this case) in included example. It happens for -march=i386, -march=i486, -march=i586 and -march=k6, but not for -march=i686. I'm getting output: 245 19 instead of correct: 42 1 Andris #include <stdio.h> struct foo { unsigned a:8, b:8; }; struct foo div10 (unsigned short arg); int main (void) { struct foo bar = div10(421); printf ("%u %u\n", (unsigned) bar.a, (unsigned) bar.b); } struct foo div10 (unsigned short arg) { struct foo bar; bar.a = arg/10; bar.b = arg%10; return bar; } >How-To-Repeat: gcc -O2 -march=i386 foo.c -o foo ./foo (the same for i486, i586 and k6). >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-11-13 17:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-02 7:21 pavenis [this message] 2002-02-21 8:11 jakub
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=20011113171639.18597.qmail@sourceware.cygnus.com \ --to=pavenis@latnet.lv \ --cc=gcc-gnats@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).