From: Jamie Lokier <egcs@tantalophile.demon.co.uk>
To: Tim Hollebeek <tim@franck.Princeton.EDU>
Cc: george@moberg.com, egcs@egcs.cygnus.com
Subject: Re: Clarification anyone? -- was Re: Linux and aliasing?
Date: Tue, 08 Jun 1999 08:24:00 -0000 [thread overview]
Message-ID: <19990608172448.A6200@pcep-jamie.cern.ch> (raw)
In-Reply-To: <199906081731.KAA16675@franck.Princeton.EDU>
Tim Hollebeek wrote:
> This is actually suprisingly useful information for a compiler.
Indeed, this is why we want to use the information to do really clever
optimisations, while also doing the right thing on traditional code.
We have to draw the line between traditional code that's going to keep
working and code that's going to break. That's what the thread's about.
-- Jamie
WARNING: multiple messages have this Message-ID
From: Jamie Lokier <egcs@tantalophile.demon.co.uk>
To: Tim Hollebeek <tim@franck.Princeton.EDU>
Cc: george@moberg.com, egcs@egcs.cygnus.com
Subject: Re: Clarification anyone? -- was Re: Linux and aliasing?
Date: Wed, 30 Jun 1999 15:43:00 -0000 [thread overview]
Message-ID: <19990608172448.A6200@pcep-jamie.cern.ch> (raw)
Message-ID: <19990630154300.UYbOqkzC3bnfFIMcfipU2A9CkCMNJPtW7umK-ZXEdb0@z> (raw)
In-Reply-To: <199906081731.KAA16675@franck.Princeton.EDU>
Tim Hollebeek wrote:
> This is actually suprisingly useful information for a compiler.
Indeed, this is why we want to use the information to do really clever
optimisations, while also doing the right thing on traditional code.
We have to draw the line between traditional code that's going to keep
working and code that's going to break. That's what the thread's about.
-- Jamie
next prev parent reply other threads:[~1999-06-08 8:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-08 6:42 george
1999-06-08 7:33 ` Tim Hollebeek
1999-06-08 8:24 ` Jamie Lokier [this message]
1999-06-30 15:43 ` Jamie Lokier
1999-06-08 10:33 ` Nick Ing-Simmons
1999-06-08 10:41 ` mark
1999-06-08 15:47 ` Martin v. Loewis
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` mark
1999-06-30 15:43 ` Nick Ing-Simmons
1999-06-30 15:43 ` Tim Hollebeek
1999-06-08 10:20 ` mark
1999-06-08 13:50 ` Ross Smith
1999-06-09 0:40 ` Martin v. Loewis
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` Ross Smith
1999-06-30 15:43 ` mark
1999-06-08 15:06 ` Martin v. Loewis
1999-06-11 10:01 ` James Antill
1999-06-30 15:43 ` James Antill
1999-06-30 15:43 ` Martin v. Loewis
1999-06-30 15:43 ` george
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=19990608172448.A6200@pcep-jamie.cern.ch \
--to=egcs@tantalophile.demon.co.uk \
--cc=egcs@egcs.cygnus.com \
--cc=george@moberg.com \
--cc=tim@franck.Princeton.EDU \
/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).