public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Peter Barada <pbarada@mail.wm.sps.mot.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/8309:m68k-elf-gcc -m5200 produces erroneous SImode set of short varaible on stack Date: Tue, 29 Oct 2002 15:56:00 -0000 [thread overview] Message-ID: <20021029235600.12724.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8309; it has been noted by GNATS. From: Peter Barada <pbarada@mail.wm.sps.mot.com> To: gcc-gnats@gcc.gnu.org Cc: Peter.Barada@motorola.com Subject: Re: target/8309:m68k-elf-gcc -m5200 produces erroneous SImode set of short varaible on stack Date: Tue, 29 Oct 2002 18:49:50 -0500 I've culled a much smaller testcase that fails on the trunk and the 3.2 branch. I'm backsearching the trunk to see when this bug was introduced, and have found the bug existed back at 2000/02/01, but doesn't show itself at 1999/01/01, so I'll try to narrow it down. #define SMALLER_TESTCASE /* make the testcase *very* small */ extern void foo(); void foo(a,b,c,d,e,f,g,h,i,j,k,l) short a,b,c,d,e,f,g,h,i,j,k,l; { short m,n,o,p,q,r,s #ifndef SMALLER_TESTCASE ,t,u,v #endif ; for (m=0; m<a; ++m) { for (n=m; n<b; ++n) { for (o=n; o<c; ++o) { for (p=o; p<d; ++p) { for (q=p; q<e; ++q) { for (r=q; r<f; ++r) { for (s=r; s<g; ++s) { #ifndef SMALLER_TESTCASE for (t=s; t<h; ++t) { for (u=t; u<i; ++u) { for (v=u; v<j; ++v) { #endif foo2(m,n,o,p,q ,r,s #ifndef SMALLER_TESTCASE ,t,u,v #endif ); } } #ifndef SMALLER_TESTCASE } } } #endif } } } } } }
next reply other threads:[~2002-10-29 23:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-29 15:56 Peter Barada [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-22 11:46 target/8309: m68k-elf-gcc " Peter.Barada
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=20021029235600.12724.qmail@sources.redhat.com \ --to=pbarada@mail.wm.sps.mot.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).