From: Olivier Hainque <hainque@ACT-Europe.FR>
To: Franz.Sirl-kernel@lauterbach.com
Cc: gcc@gcc.gnu.org
Subject: Problem with recent fixes in loop_iterations ?
Date: Tue, 27 Nov 2001 09:26:00 -0000 [thread overview]
Message-ID: <kthergm8fi.fsf@berlin.int.act-europe.fr> (raw)
Message-ID: <20011127092600.Ba3e7hcMhUujw3TRfozSIiOor4vbqg5sKDvQrUq0LCQ@z> (raw)
Hello,
Hoping you would be able to help with a problem we face :)
Trying to bootstrap Ada on hpux with our internal GNAT tree leads to
SEGV from within loop_iterations. Basically, we get to
/* If there are multiple conditionalized loop exit tests, they may jump
back to differing CODE_LABELs. */
if (loop->top && loop->cont)
{
rtx temp = PREV_INSN (last_loop_insn);
do
{
if (GET_CODE (temp) == JUMP_INSN
/* Previous unrolling may have generated new insns not covered
by the uid_luid array. */
&& INSN_UID (JUMP_LABEL (temp)) < max_uid_for_loop
with a temp looking like the following :
(jump_insn 5407 5406 5408 (addr_vec:DI[
(label_ref:SI 5389)
...
GET_CODE (temp) is indeed JUMP_INSN, but the associated JUMP_LABEL is NULL
and INSN_UID dereferences it.
Is having this kind of insn here something expected never to happen ... or
should the test be refined, or ... ?
Thank you very much in advance for your help,
Kind Regards,
Olivier Hainque
--
hainque@act-europe.fr
next reply other threads:[~2001-11-27 9:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-18 20:37 Olivier Hainque [this message]
2001-11-19 9:05 ` Richard Henderson
2001-11-21 13:41 ` Olivier Hainque
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=kthergm8fi.fsf@berlin.int.act-europe.fr \
--to=hainque@act-europe.fr \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc@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).