public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@cygnus.com>
To: law@cygnus.com
Cc: Jim Wilson <wilson@cygnus.com>,
	kkaempf@progis.de, egcs@cygnus.com, rth@cygnus.com
Subject: Re: egcs 2.91.14: packed-1 failure on openvms/alpha, more info
Date: Mon, 30 Mar 1998 16:18:00 -0000	[thread overview]
Message-ID: <19980330145218.21981@dot.cygnus.com> (raw)
In-Reply-To: <11591.890955234@hurl.cygnus.com>

On Thu, Mar 26, 1998 at 04:33:54PM -0700, Jeffrey A Law wrote:
> Who knows, that code might even be totally useless now that we
> propagate alias information better.

Is that the same code that records "known alignment" of pointers
in registers?  That information is still useful, though the way
we keep track of it seems truely ugly.


r~

  reply	other threads:[~1998-03-30 16:18 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
1998-03-30 16:18         ` Richard Henderson [this message]
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=19980330145218.21981@dot.cygnus.com \
    --to=rth@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=kkaempf@progis.de \
    --cc=law@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).