public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/12845] [3.4 Regression] Error: Invalid Compare and Branch Condition
Date: Wed, 24 Dec 2003 21:55:00 -0000 [thread overview]
Message-ID: <20031224215422.9582.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031030183500.12845.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2003-12-24 21:54 -------
Subject: Re: [3.4 Regression] Error: Invalid Compare
> Can this now be closed?
While I have fixed the code generation issue in the PA backend, the
optimization issue hasn't been fixed as far as I know.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12845
next prev parent reply other threads:[~2003-12-24 21:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 19:31 [Bug optimization/12845] New: " danglin at gcc dot gnu dot org
2003-10-30 19:52 ` [Bug optimization/12845] [3.4 Regression] " pinskia at gcc dot gnu dot org
2003-11-02 20:59 ` danglin at gcc dot gnu dot org
2003-11-02 21:01 ` danglin at gcc dot gnu dot org
2003-11-02 21:02 ` danglin at gcc dot gnu dot org
2003-11-02 21:38 ` cvs-commit at gcc dot gnu dot org
2003-11-04 14:26 ` pinskia at gcc dot gnu dot org
2003-12-24 16:19 ` kazu at cs dot umass dot edu
2003-12-24 21:55 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2004-01-01 6:06 ` pinskia at gcc dot gnu dot org
2004-01-10 11:32 ` [Bug optimization/12845] [3.4 Regression] missed jump optimization steven at gcc dot gnu dot org
2004-01-13 4:18 ` pinskia at gcc dot gnu dot org
2004-01-14 14:45 ` dave at hiauly1 dot hia dot nrc dot ca
2004-03-16 16:23 ` [Bug optimization/12845] [3.4/3.5 " mmitchel at gcc dot gnu dot org
2004-06-18 23:42 ` [Bug rtl-optimization/12845] " mmitchel at gcc dot gnu dot org
2004-06-19 0:13 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-29 19:02 ` mmitchel at gcc dot gnu dot org
2004-11-01 0:45 ` [Bug rtl-optimization/12845] [3.4/4.0 " mmitchel at gcc dot gnu dot org
2004-12-13 18:58 ` kazu at cs dot umass dot edu
2004-12-13 19:08 ` dave at hiauly1 dot hia dot nrc dot ca
2005-01-31 13:55 ` kazu at cs dot umass dot edu
2005-02-02 5:50 ` [Bug rtl-optimization/12845] [3.4 " ian at airs dot com
2005-02-02 12:24 ` giovannibajo at libero dot it
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=20031224215422.9582.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: link
Be 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).