public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/14470] [tree-ssa] trouble with post-increment
Date: Sat, 20 Mar 2004 13:40:00 -0000 [thread overview]
Message-ID: <20040320134056.26097.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040307221314.14470.lvoge@cs.vu.nl>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-03-20 13:40 -------
Well, nesting levels might be overkill. It appears that marking the queue is
sufficient.
Richard, the attached patch fixes the problem for the testcase you submitted.
Could you see if it restores the initial state of CSiBE on ARM? TIA.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14470
next prev parent reply other threads:[~2004-03-20 13:40 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 22:13 [Bug c/14470] New: x86 optimizer error (?) lvoge at cs dot vu dot nl
2004-03-07 22:26 ` [Bug c/14470] " lvoge at cs dot vu dot nl
2004-03-07 22:36 ` bangerth at dealii dot org
2004-03-07 22:43 ` lvoge at cs dot vu dot nl
2004-03-07 22:56 ` giovannibajo at libero dot it
2004-03-07 23:12 ` falk at debian dot org
2004-03-07 23:19 ` lvoge at cs dot vu dot nl
2004-03-07 23:57 ` pinskia at gcc dot gnu dot org
2004-03-08 0:57 ` pinskia at gcc dot gnu dot org
2004-03-08 1:47 ` amodra at bigpond dot net dot au
2004-03-08 3:12 ` zack at gcc dot gnu dot org
2004-03-08 4:35 ` bangerth at dealii dot org
2004-03-08 5:05 ` giovannibajo at libero dot it
2004-03-08 5:30 ` zack at gcc dot gnu dot org
2004-03-08 9:13 ` [Bug optimization/14470] [3.4/3.5 regression] trouble with post-increment reichelt at gcc dot gnu dot org
2004-03-08 9:17 ` [Bug optimization/14470] [3.3/3.4/3.5 " reichelt at gcc dot gnu dot org
2004-03-08 9:37 ` ebotcazou at gcc dot gnu dot org
2004-03-08 10:13 ` jsm at polyomino dot org dot uk
2004-03-11 6:34 ` [Bug middle-end/14470] " ebotcazou at gcc dot gnu dot org
2004-03-13 2:53 ` [Bug middle-end/14470] [3.4 " gdr at gcc dot gnu dot org
2004-03-13 3:03 ` cvs-commit at gcc dot gnu dot org
2004-03-13 16:20 ` [Bug middle-end/14470] [3.4/3.5 regression] [tree-ssa] " mmitchel at gcc dot gnu dot org
2004-03-13 18:16 ` cvs-commit at gcc dot gnu dot org
2004-03-13 18:26 ` [Bug middle-end/14470] [3.4 " cvs-commit at gcc dot gnu dot org
2004-03-13 18:26 ` pinskia at gcc dot gnu dot org
2004-03-13 18:29 ` [Bug middle-end/14470] " pinskia at gcc dot gnu dot org
2004-03-13 18:32 ` cvs-commit at gcc dot gnu dot org
2004-03-13 18:42 ` ebotcazou at gcc dot gnu dot org
2004-03-13 18:52 ` pinskia at gcc dot gnu dot org
2004-03-13 19:01 ` ebotcazou at gcc dot gnu dot org
2004-03-19 15:56 ` rearnsha at gcc dot gnu dot org
2004-03-19 17:04 ` mmitchel at gcc dot gnu dot org
2004-03-19 17:07 ` rearnsha at arm dot com
2004-03-19 17:09 ` richard dot earnshaw at arm dot com
2004-03-19 17:59 ` ebotcazou at gcc dot gnu dot org
2004-03-19 17:59 ` ebotcazou at gcc dot gnu dot org
2004-03-19 23:26 ` ebotcazou at gcc dot gnu dot org
2004-03-20 13:40 ` ebotcazou at gcc dot gnu dot org [this message]
2004-03-21 19:26 ` mmitchel at gcc dot gnu dot org
2004-03-22 11:59 ` cvs-commit at gcc dot gnu dot org
2004-03-22 12:09 ` cvs-commit at gcc dot gnu dot org
2004-03-22 16:31 ` ebotcazou at gcc dot gnu dot org
2004-03-22 18:40 ` cvs-commit at gcc dot gnu dot org
2004-05-01 1:38 ` dnovillo at gcc dot gnu dot org
2004-05-03 14:42 ` dnovillo at gcc dot gnu dot org
2004-05-03 15:05 ` bangerth at dealii dot org
2004-05-03 15:09 ` dnovillo at redhat dot com
2004-05-03 15:12 ` reichelt at gcc dot gnu dot org
2004-05-03 15:13 ` reichelt at gcc dot gnu dot org
2004-05-03 15:31 ` bangerth at dealii dot org
2004-05-13 21:52 ` [Bug tree-optimization/14470] " pinskia at gcc dot gnu dot org
2004-09-14 22:58 ` dnovillo at gcc dot gnu dot org
2004-09-17 3:53 ` pinskia at gcc dot gnu dot org
2004-09-18 15:44 ` dnovillo 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=20040320134056.26097.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).