public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/8299: [sh-gcc] Optimizing problem Date: Sat, 10 May 2003 08:56:00 -0000 [thread overview] Message-ID: <20030510085601.4319.qmail@sources.redhat.com> (raw) The following reply was made to PR target/8299; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: tanaka@personal-media.co.jp, gcc-gnats@gcc.gnu.org Cc: Subject: Re: target/8299: [sh-gcc] Optimizing problem Date: Sat, 10 May 2003 01:49:53 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=8299 Hello, could the submitter of this report please determine whether this problem occurs in more current versions of gcc (3.2.3, or 3.3 prerelease). If so, could the submitter please provide a sample of the assembly output that should be produced for this testcase, but isn't? Thanks, Dara
next reply other threads:[~2003-05-10 8:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-10 8:56 Dara Hazeghi [this message] 2003-05-12 11:46 giovannibajo
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=20030510085601.4319.qmail@sources.redhat.com \ --to=dhazeghi@yahoo.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).