Leopold Toetsch wrote:
> Am Mittwoch, 20. Dezember 2006 20:24 schrieb Ron Blaschke:
>> - The assertion seems to check that the lowest two bits of a function
>> pointer are zero. Why's that?
>
> That's a bigger hack to discern function from PMC pointers in that table.
> That
> hack and the whole
Am Mittwoch, 20. Dezember 2006 20:24 schrieb Ron Blaschke:
> - The assertion seems to check that the lowest two bits of a function
> pointer are zero. Why's that?
That's a bigger hack to discern function from PMC pointers in that table. That
hack and the whole table needs to be replaced by a mor
chromatic wrote:
> On Wednesday 20 December 2006 11:24, Ron Blaschke wrote:
>
>> - The assertion seems to check that the lowest two bits of a function
>> pointer are zero. Why's that?
>
> Presumably because pointers need a specific alignment, so those two bits will
> always be zero on a raw poi
On Wednesday 20 December 2006 11:24, Ron Blaschke wrote:
> - The assertion seems to check that the lowest two bits of a function
> pointer are zero. Why's that?
Presumably because pointers need a specific alignment, so those two bits will
always be zero on a raw pointer -- and thus, they're ava
Sorry to bring this up again, but I hope someone can help me with this.
I'm trying to compile Parrot on Windows XP / Visual C++ with assertions
enabled, that is, without C.
When running miniparrot I receive the following error:
Assertion failed: (PTR2UINTVAL(mmd_table[i].func_ptr) & 3) == 0, fil
