public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Peter van Hoof <p.van-hoof@qub.ac.uk> To: toon@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: fortran/8751: g77 produces incorrect code when using -funroll-loops Date: Sat, 01 Mar 2003 21:36:00 -0000 [thread overview] Message-ID: <20030301213601.20602.qmail@sources.redhat.com> (raw) The following reply was made to PR fortran/8751; it has been noted by GNATS. From: Peter van Hoof <p.van-hoof@qub.ac.uk> To: toon@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, p.van-hoof@qub.ac.uk, toon@gcc.gnu.org, toon@moene.indiv.nluug.nl, gcc-gnats@gcc.gnu.org Cc: Subject: Re: fortran/8751: g77 produces incorrect code when using -funroll-loops Date: Sat, 01 Mar 2003 21:28:05 +0000 I downloaded gcc version 3.4 20030301 (experimental) via CVS which contains the new loop unroller. When I compiled and executed the program with this compiler, it still behaved exactly the same as described in the original bug report. Hence it seems that the new loop unroller does not solve this particular problem. Cheers, Peter.
next reply other threads:[~2003-03-01 21:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-01 21:36 Peter van Hoof [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-01 10:19 toon
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=20030301213601.20602.qmail@sources.redhat.com \ --to=p.van-hoof@qub.ac.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=toon@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).