[Issue 8536] OPTLINK crash with large fixed-size array

d-bugmail at puremagic.com d-bugmail at puremagic.com
Fri Aug 10 16:01:10 PDT 2012


http://d.puremagic.com/issues/show_bug.cgi?id=8536


Walter Bright <bugzilla at digitalmars.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla at digitalmars.com


--- Comment #1 from Walter Bright <bugzilla at digitalmars.com> 2012-08-10 16:01:07 PDT ---
This is a well known Optlink bug, though I don't have the bugzilla number
handy.

You're wrong about it impeding optimizations compared with dynamically
allocating it, for a couple reasons:

1. static data is often indirectly accessed through a register anyway, either
in explicit code generated by the compiler, or implicitly as how the CPU does
virtual memory, or even there's no way to do it other than offsetting the
program counter register

2. there is no performance penalty for offsetting a base address register
versus and addressing mode with just and address.

D knows the static compile time sizes of arrays if you use static arrays.
That's what they're for.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list