public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: tm <tm@mail.kloo.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/6225: [x86 x sh-elf] reload1.c failure Date: Fri, 29 Nov 2002 17:36:00 -0000 [thread overview] Message-ID: <20021121025601.11978.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/6225; it has been noted by GNATS. From: tm <tm@mail.kloo.net> To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gniibe@m17n.org, jh@suse.cz, nobody@gcc.gnu.org, tm@kloo.net, gcc-gnats@gcc.gnu.org Cc: Subject: Re: bootstrap/6225: [x86 x sh-elf] reload1.c failure Date: Wed, 20 Nov 2002 18:45:21 -0800 (PST) On 21 Nov 2002 bangerth@dealii.org wrote: > Old Synopsis: reload1.c failure for sh-elf. Bootstrap failure on sh4-unknown-linux-gnu > New Synopsis: [x86 x sh-elf] reload1.c failure > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Wed Nov 20 18:08:49 2002 > State-Changed-Why: > This is a rather old bootstrap failure. Can you please check > whether this still happens with newer versions of gcc and > report back to us what you find? > > Has the patch you mention in your report been applied in > the meantime? > > Thanks > Wolfgang > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6225 > I've tested the testcase against CVS head, specifically: gcc version 3.3 20021119 (experimental) and the resultant output code compiled with -O2 seems correct: .L232: .loc 1 288 0 mov #64,r6 add r14,r6 mov.l @(12,r6),r0 mov.l @(8,r6),r6 sub r6,r0 mov #64,r6 add r14,r6 mov.l r0,@(8,r6) <- r14 + 64 + 8 = r14 + 72 = correct This seems ok to close. Toshi
next reply other threads:[~2002-11-21 2:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-29 17:36 tm [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-30 4:26 bangerth 2002-11-29 10:36 bangerth
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=20021121025601.11978.qmail@sources.redhat.com \ --to=tm@mail.kloo.net \ --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).