public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Peter van Hoof <p.van-hoof@qub.ac.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/10312: optimizer creates wrong code for loop Date: Fri, 04 Apr 2003 19:16:00 -0000 [thread overview] Message-ID: <20030404191601.11392.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/10312; it has been noted by GNATS. From: Peter van Hoof <p.van-hoof@qub.ac.uk> To: ebotcazou@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, p.van-hoof@qub.ac.uk, gcc-gnats@gcc.gnu.org Cc: Subject: Re: optimization/10312: optimizer creates wrong code for loop Date: Fri, 04 Apr 2003 20:08:39 +0100 > Does passing -fno-gcse-sm cure the problem? Yes, that cures the problem. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10312 -- Peter van Hoof APS Division - Physics Department Queen's University of Belfast Belfast BT7 1NN Northern Ireland Home Page: http://star.pst.qub.ac.uk/~pvh
next reply other threads:[~2003-04-04 19:16 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-04 19:16 Peter van Hoof [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-04 22:06 Eric Botcazou 2003-04-04 19:03 ebotcazou 2003-04-04 18:56 p.van-hoof
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=20030404191601.11392.qmail@sources.redhat.com \ --to=p.van-hoof@qub.ac.uk \ --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).