From: Steve Ellcey <sje@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: optimization/3783
Date: Wed, 01 Aug 2001 22:02:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005982@msgid-missing> (raw)
FYI: I have spent a little time looking at this bug, I haven't got a
fix but I did create a smaller test program that I am including in this
mail. Running it on HP-UX IA64 it looks like the optimizer is going
into an infinite loop in canon_rtx because one of the entries (REG 351
in my case) is set to be a plus RTX of REG 351 and CONST 1. How that
self-referential access got in there, I don't know but it seems to be
the cause of the problem. Anyway I thought I would just send off what
I know and the smaller test case before going off on some vacation.
Steve Ellcey
sje@cup.hp.com
extern struct buffer_headX *udf_read_taggedX(unsigned short *);
#pragma pack(1)
typedef struct {
unsigned int extLength;
unsigned int extLocation;
} extent_adX;
#pragma pack()
struct super_blockX {
unsigned long s_blocksize;
unsigned char s_blocksize_bits;
unsigned char s_dirt;
};
struct buffer_headX {
struct buffer_head *b_next;
unsigned long b_blocknr;
unsigned short b_size;
unsigned short b_list;
};
static void
udf_load_logicalvolintX(struct super_blockX *sb, extent_adX loc)
{
struct buffer_headX *bh = ((void *)0);
unsigned short ident;
while ((bh = udf_read_taggedX(&ident)) && loc.extLength > 0)
{
loc.extLength -= sb->s_blocksize;
loc.extLocation ++;
}
}
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr783&database=gcc
next reply other threads:[~2001-08-01 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 22:02 Steve Ellcey [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-04 20:33 [Linux-ia64] Re: optimization/3783 Jessica Han
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=marc-linux-ia64-105590693005982@msgid-missing \
--to=sje@cup.hp.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.