From: Sean Quinlan <seanq@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan or side effect
Date: Wed, 27 Feb 2002 10:27:58 -0500 [thread overview]
Message-ID: <3C7CFAFE.4996DA2A@research.bell-labs.com> (raw)
In-Reply-To: <d1d1b1fb6844728c522ac30443f2fd89@plan9.bell-labs.com>
My experience is that most, if not all, optimizing C
compilers will make optimistic assumptions about aliasing.
Given that C allows arbitrary cast and application of the &
operator, it is pretty much impossible to excatly determine
what can be aliased. The compiler takes a shot at figuring this
out, but in general, it has to be optimistic if it is going
to find many variables that can be registerised.
For example, I believe the plan 9 compilers is a little
optimistic with globals. The compiler will registerise
such variables within a function even though it is possible
that the variable is aliased via a pointer. I recall
Ken saying he never gets caught, but obviously it is not
hard to contrive examples when he will get the "wrong"
answer.
presotto@plan9.bell-labs.com wrote:
>
> Bushnell et al,
>
> By the way, I'm not ignoring Thomas' question.
> I'm querying compiler designers I know about my
> statement that they know that they might be breaking
> programs, i.e. generating incorrect code,
> with some optimizations and find that acceptable.
> It was definitely a true statement when I was at
> DG in the compiler group, but that was a long
> time ago. It could be that I'm assuming a plan when
> all I'm seeing is the inevitable bugs.
next prev parent reply other threads:[~2002-02-27 15:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 15:08 presotto
2002-02-27 15:27 ` Sean Quinlan [this message]
2002-02-28 9:58 ` Thomas Bushnell, BSG
2002-02-28 12:51 ` Ralph Corderoy
2002-02-28 16:57 ` Thomas Bushnell, BSG
2002-02-28 16:01 ` AMSRL-CI-CN
2002-02-28 16:52 ` Thomas Bushnell, BSG
2002-02-28 17:41 David Gordon Hogan
2002-03-01 10:02 ` Thomas Bushnell, BSG
2002-03-01 12:07 ` Boyd Roberts
2002-03-04 10:04 ` Thomas Bushnell, BSG
2002-03-04 17:11 ` Sean Quinlan
2002-03-04 18:23 ` ozan s yigit
2002-03-05 9:41 ` Thomas Bushnell, BSG
2002-03-05 9:56 ` Boyd Roberts
2002-03-05 9:43 ` Boyd Roberts
2002-03-08 17:30 ` Thomas Bushnell, BSG
2002-03-08 18:00 ` Dan Cross
2002-03-11 10:04 ` Ralph Corderoy
2002-03-11 10:04 ` Thomas Bushnell, BSG
2002-03-01 11:57 ` Boyd Roberts
2002-03-01 11:35 forsyth
2002-03-05 9:54 Fco.J.Ballesteros
2002-03-06 9:51 ` Thomas Bushnell, BSG
2002-03-06 9:52 ` Douglas A. Gwyn
2002-03-08 9:59 ` ozan s. yigit
2002-03-06 10:24 geoff
2002-03-07 9:56 ` Douglas A. Gwyn
2002-03-07 13:45 rob pike
2002-03-07 15:47 ` AMSRL-CI-C
2002-03-08 19:22 forsyth
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=3C7CFAFE.4996DA2A@research.bell-labs.com \
--to=seanq@research.bell-labs.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).