[m-rev.] for review: use bytecode for procedure body representations
Zoltan Somogyi
zs at cs.mu.OZ.AU
Fri Apr 1 11:54:49 AEST 2005
On 31-Mar-2005, Julien Fischer <juliensf at cs.mu.OZ.AU> wrote:
> This change causes the C compiler to spit out a large number of warnings
> about structure initialization from incompatible pointer types. (This
> is occurring when compiling the runtime/library in the .decldebug grades).
>
> The C compiler is complains about the line marked #### below. The type
> of this field was changed in this diff from `MR_Word *' to
> `const MR_uint_least8_t *' but as far as I can tell MR_TAG_COMMON(0,279)
> will still have type `MR_Word *'.
>
> static MR_STATIC_CODE_CONST MR_Exec_Trace
> mercury_data__proc_layout_exec_trace__fn__float__multiply_by_pow_3_0 = {
> MR_LABEL_LAYOUT_REF(fn__float__multiply_by_pow_3_0_i2),
> (const MR_Module_Layout *) &mercury_data__module_layout__float,
> MR_TAG_COMMON(0,279), ####
That is because the typedef in the runtime is from after the change, but the
compiler generating that code is from before the change. The problem will
go away when the installed compiler is compatible with the runtime.
Zoltan.
--------------------------------------------------------------------------
mercury-reviews mailing list
post: mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------
More information about the reviews
mailing list