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/10775: m32r-elf-gcc -O3 (regrename) used lr in leaf-functions without saving Date: Wed, 14 May 2003 18:16:00 -0000 [thread overview] Message-ID: <20030514181602.4850.qmail@sources.redhat.com> (raw) The following reply was made to PR target/10775; it has been noted by GNATS. From: Dara Hazeghi <dhazeghi@yahoo.com> To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, inaoka.kazuhiro@renesas.com Cc: Subject: Re: target/10775: m32r-elf-gcc -O3 (regrename) used lr in leaf-functions without saving Date: Wed, 14 May 2003 11:11:00 -0700 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=10775 Hello, gcc 3.3 is in the process of being released. Would it be possible for you to check whether the error still occurs with that version? Thanks, Dara
next reply other threads:[~2003-05-14 18:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-14 18:16 Dara Hazeghi [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-15 10:56 Kazuhiro Inaoka 2003-05-14 6:16 inaoka.kazuhiro
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=20030514181602.4850.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).