www.digitalmars.com Home | Search | C & C++ | D | DMDScript | News Groups | index | prev | next
Archives

D Programming
D
D.gnu
digitalmars.D
digitalmars.D.bugs
digitalmars.D.dtl
digitalmars.D.dwt
digitalmars.D.announce
digitalmars.D.learn
digitalmars.D.debugger

C/C++ Programming
c++
c++.announce
c++.atl
c++.beta
c++.chat
c++.command-line
c++.dos
c++.dos.16-bits
c++.dos.32-bits
c++.idde
c++.mfc
c++.rtl
c++.stl
c++.stl.hp
c++.stl.port
c++.stl.sgi
c++.stlsoft
c++.windows
c++.windows.16-bits
c++.windows.32-bits
c++.wxwindows

digitalmars.empire
digitalmars.DMDScript

D - aliasing

↑ ↓ ← "Sean L. Palmer" <spalmer iname.com> writes:
Walter, is there anything at all that can be done about the problem of
missed optimization opportunities due to the issue of potential aliasing?
Should D assume aliasing is happening, as C does?  Or can the compiler just
figure out there's no possiblity of aliasing for a given block of code?

Sean
Nov 12 2001
↑ ↓ → "Walter" <walter digitalmars.com> writes:
"Sean L. Palmer" <spalmer iname.com> wrote in message
news:9so1oe$n85$1 digitaldaemon.com...
 Walter, is there anything at all that can be done about the problem of
 missed optimization opportunities due to the issue of potential aliasing?
 Should D assume aliasing is happening, as C does?  Or can the compiler

 figure out there's no possiblity of aliasing for a given block of code?

Aliasing will be explicitly disallowed in array operations, which will enable optimizers to use parallel coding techniques.
Nov 12 2001