public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: saito@densan.co.jp To: gcc-gnats@gcc.gnu.org Subject: c/8397: sh-coff-gcc-3.2 Date: Wed, 30 Oct 2002 01:06:00 -0000 [thread overview] Message-ID: <20021030085908.10832.qmail@sources.redhat.com> (raw) >Number: 8397 >Category: c >Synopsis: sh-coff-gcc-3.2 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: wrong-code >Submitter-Id: net >Arrival-Date: Wed Oct 30 01:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Hideo Saito >Release: gcc-3.2 >Organization: >Environment: NetBSD/PowerPC-1.5.2 gcc-3.0.3 >Description: If the size of the automatic variables becomes large when there is no flag specification of optimization, the code which accesses the variable which made a register declaration is wrong. source code: len -= size; generated assembler code: mov #64,r2 add r14,r2 mov #64,r2 add r14,r2 mov.l @(4,r2),r1 mov.l @(8,r2),r2 sub r2,r1 mov.l r1,@(4,r2) bra L2 nop >How-To-Repeat: compile: sh-coff-gcc -S fff.c fff.c: see below fff(len, size) register int len; register int size; { char buf[58]; char *ps; char *pe; while (len < size) { len -= size; } } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-10-30 9:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021030085908.10832.qmail@sources.redhat.com \ --to=saito@densan.co.jp \ --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).