From: Mark Mitchell <mark@markmitchell.com>
To: dje@watson.ibm.com
Cc: davem@pierdol.cobaltmicro.com, law@cygnus.com,
meissner@cygnus.com, egcs@cygnus.com
Subject: Re: PowerPC build breakage caused by 8/25/98 loop.c change
Date: Fri, 18 Sep 1998 22:10:00 -0000 [thread overview]
Message-ID: <199809182141.OAA17803@smtp.earthlink.net> (raw)
In-Reply-To: <9809182120.AA35006@marc.watson.ibm.com>
>>>>> "David" == David Edelsohn <dje@watson.ibm.com> writes:
David> I don't know enough about these changes to determine
David> what is wrong. Mark, I would appreciate if you could find
David> time to look into this. I can try to provide some help and
David> dump traces, if you want to see intermediate output.
I'd like to help. Unfortunately, I've not got access to a PowerPC
platform. Can you isolate which function is being miscompiled?
I doubt the AVOID_CCMODE_COPIES bit is to blame; if anything went
wrong with that code it would probably a trigger an immediate crash as
load_mems_and_recount_loop_regs_set runs. It sounds like you're
seeing a failure further down the line, right? But, you can easily
test that hypothesis; take your working version, and substitute just
the AVOID_CCMODE_COPIES in load_mems_and_recount_loop_regs_set.
You'll have to change `VARRAY_CHAR (may_not_optimize, i)' to
`may_not_optimize[i] = 1' since you'll not have the VARRAY stuff. If
the resulting compiler doesn't bootstrap, then we'll know that's the
problem; otherwise, it's elsewhere.
I'll take a look at the rest, but you can too: it was a
straightforward replacement of `x[i] = j' with `VARRAY_TYPE (x, i) =
j'. One possibility is that TYPE (which should be CHAR if the thing
was an array of chars, INT if ints, etc.) is wrong somewhere.
--
Mark Mitchell mark@markmitchell.com
Mark Mitchell Consulting http://www.markmitchell.com
next prev parent reply other threads:[~1998-09-18 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-18 22:10 David Edelsohn
1998-09-18 15:25 ` Jeffrey A Law
1998-09-18 22:10 ` Mark Mitchell [this message]
1998-09-18 22:10 ` David Edelsohn
1998-09-18 15:25 ` Jeffrey A Law
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=199809182141.OAA17803@smtp.earthlink.net \
--to=mark@markmitchell.com \
--cc=davem@pierdol.cobaltmicro.com \
--cc=dje@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=meissner@cygnus.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).