From: Olivier Hainque <hainque@ACT-Europe.FR>
To: Richard Henderson <rth@redhat.com>
Cc: Franz.Sirl-kernel@lauterbach.com, gcc@gcc.gnu.org
Subject: Re: Problem with recent fixes in loop_iterations ?
Date: Thu, 29 Nov 2001 01:35:00 -0000 [thread overview]
Message-ID: <kt3d2x538l.fsf@berlin.int.act-europe.fr> (raw)
Message-ID: <20011129013500.tyjbQ7_qV8xiV9p3bB_0TXrnDOaeBuclTR-T1euxDrY@z> (raw)
In-Reply-To: <20011127135333.C30114@redhat.com>
Richard Henderson <rth@redhat.com> writes:
> The test must be refined a good deal to deal with a switch statement.
> Probably you should notice the ADDR_VEC | ADDR_DIFF_VEC and give up.
This part of the compiler is not very familiar to me. By give up, you mean
returning 0, or would something like below be appropriate ? In any case,
I'll prepare a properly formed submission.
Thanks for your help,
Kind Regards,
Olivier
*** unroll.c 2001/11/27 22:09:09 1.149
--- unroll.c 2001/11/29 09:32:44
*************** loop_iterations (loop)
*** 3529,3534 ****
--- 3529,3536 ----
do
{
if (GET_CODE (temp) == JUMP_INSN
+ /* Avoid analyzing jumps not related to the loop. */
+ && JUMP_LABEL (temp) != 0
/* Previous unrolling may have generated new insns not covered
by the uid_luid array. */
&& INSN_UID (JUMP_LABEL (temp)) < max_uid_for_loop
next prev parent reply other threads:[~2001-11-29 1:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 20:37 Olivier Hainque
2001-11-19 9:05 ` Richard Henderson
2001-11-21 13:41 ` Olivier Hainque [this message]
2001-11-21 16:13 ` Richard Henderson
2001-11-29 9:53 ` Richard Henderson
2001-11-29 1:35 ` Olivier Hainque
2001-11-27 13:53 ` Richard Henderson
2001-11-27 9:26 ` Olivier Hainque
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=kt3d2x538l.fsf@berlin.int.act-europe.fr \
--to=hainque@act-europe.fr \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.com \
/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).