From: Jeffrey A Law <law@cygnus.com>
To: Jim Wilson <wilson@cygnus.com>
Cc: kkaempf@progis.de, egcs@cygnus.com, rth@cygnus.com
Subject: Re: egcs 2.91.14: packed-1 failure on openvms/alpha, more info
Date: Thu, 26 Mar 1998 18:14:00 -0000 [thread overview]
Message-ID: <11591.890955234@hurl.cygnus.com> (raw)
In-Reply-To: <199803262235.OAA09101@rtl.cygnus.com>
In message < 199803262235.OAA09101@rtl.cygnus.com >you write:
> Is this happening in reg_scan_mark_refs? We're going to need to
> throttle that code to be less aggressive for gcse anyway.
>
> yes.
OK. I'll bring over my change from devo.
In theory the whole marking of pointer registers by reg_scan_mark_refs
should be completely reworked to not lose in the presense of global
optimizations. But I haven't come up with the right conceptual model
yet.
Who knows, that code might even be totally useless now that we
propagate alias information better.
jeff
next prev parent reply other threads:[~1998-03-26 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-18 14:08 kkaempf
1998-03-25 17:22 ` Jim Wilson
1998-03-27 15:18 ` Jeffrey A Law
1998-03-26 14:38 ` Jim Wilson
1998-03-26 18:14 ` Jeffrey A Law [this message]
1998-03-30 16:18 ` Richard Henderson
1998-03-30 16:18 ` Jeffrey A Law
1998-04-02 11:32 ` Jim Wilson
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=11591.890955234@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=kkaempf@progis.de \
--cc=rth@cygnus.com \
--cc=wilson@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).