public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/11599] gcc generates wrong code when predicate are used Date: Mon, 21 Jul 2003 17:56:00 -0000 [thread overview] Message-ID: <20030721175618.30013.qmail@sources.redhat.com> (raw) In-Reply-To: <20030719234032.11599.hjl@lucon.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11599 ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2003-07-21 17:56 ------- Subject: Bug 11599 CVSROOT: /cvs/gcc Module name: gcc Branch: gcc-3_3-branch Changes by: hjl@gcc.gnu.org 2003-07-21 17:56:14 Modified files: gcc : ChangeLog gcc/config/ia64: ia64.md Log message: 2003-07-21 H.J. Lu <hongjiu.lu@intel.com> PR optimization/11599 * config/ia64/ia64.md (prefetch): Support predicate. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.16114.2.679&r2=1.16114.2.680 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/ia64/ia64.md.diff?cvsroot=gcc&only_with_tag=gcc-3_3-branch&r1=1.94.4.6&r2=1.94.4.7
next prev parent reply other threads:[~2003-07-21 17:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-19 23:40 [Bug target/11599] New: ia64: gcc generates wrong code when predicate is used hjl at lucon dot org 2003-07-19 23:41 ` [Bug target/11599] " hjl at lucon dot org 2003-07-19 23:52 ` [Bug optimization/11599] " pinskia at physics dot uc dot edu 2003-07-20 5:04 ` [Bug optimization/11599] gcc generates wrong code when builtins are used hjl at lucon dot org 2003-07-20 12:00 ` [Bug optimization/11599] gcc generates wrong code when predicate " pinskia at physics dot uc dot edu 2003-07-20 17:12 ` falk at debian dot org 2003-07-21 17:56 ` cvs-commit at gcc dot gnu dot org [this message] 2003-07-21 18:17 ` pinskia at gcc dot gnu dot org 2003-07-25 16:31 ` jbuck at gcc dot gnu dot org
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=20030721175618.30013.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).