public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com> To: rearnsha@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: optimization/2903: Optimization bug with long long arithmetic Date: Mon, 16 Jul 2001 02:36:00 -0000 [thread overview] Message-ID: <20010716093601.19130.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR optimization/2903; it has been noted by GNATS. From: Richard Earnshaw <rearnsha@arm.com> To: Sean McNeil <sean@mcneil.com> Cc: rearnsha@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/2903: Optimization bug with long long arithmetic Date: Mon, 16 Jul 2001 10:29:00 +0100 > The tail end portion of the patch causes a build error. I am building > the compiler now without it and will let you know if it works. > > *************** > *** 9236,9243 **** > > ;; V5E instructions. > > ! (define_insn "prefetch" > ! [(unspec_volatile > [(match_operand:SI 0 "offsettable_memory_operand" "o")] > VUNSPEC_PREFETCH)] "TARGET_ARM && arm_arch5e" > "pld\\t%0") > --- 9236,9242 ---- > > ;; V5E instructions. > > ! (define_insn "ppec_volatile > [(match_operand:SI 0 "offsettable_memory_operand" "o")] > VUNSPEC_PREFETCH)] "TARGET_ARM && arm_arch5e" > "pld\\t%0") > I've no idea where that came from. It certainly isn't a change I remember making, and it is definitely wrong anyway. Thanks for pointing out the problem. R
next reply other threads:[~2001-07-16 2:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-16 2:36 Richard Earnshaw [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-01-27 16:16 Craig Rodrigues 2001-07-11 10:53 rearnsha 2001-05-22 11:56 sean
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=20010716093601.19130.qmail@sourceware.cygnus.com \ --to=rearnsha@arm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=rearnsha@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).