Janus Weil wrote:
Build and regtested on x86-64-gnu-linux.
OK for the trunk?
I think this patch is ok. Just one nit:
@@ -5571,7 +5569,7 @@ gfc_dump_module (const char *name, int dump_flag)
FIXME: For backwards compatibility with the old uncompressed
module format, write an extra e
Hi Tobias,
> Small re-diff - but essentially unchanged.
>
> (I made a thinko when adding a _final call to
> gfc_trans_class_array_init_assign: Not in all contexts the _final should be
> called, only for INTENT(OUT). Thus, I remove the _final call and deferred it
> to the actual finalization call.
Small re-diff - but essentially unchanged.
(I made a thinko when adding a _final call to
gfc_trans_class_array_init_assign: Not in all contexts the _final should
be called, only for INTENT(OUT). Thus, I remove the _final call and
deferred it to the actual finalization call. [That also matches
Pre-remark: This patch does *not* enable finalization or polymorphic
deallocation.
* * *
Dear all,
The attached patch is a bit boring and invasive, but it paves the way to
FINAL support.
Changes of technical kind:
* Changed ABI for CLASS's virtual table (due to _final) - and, hence, it
bu
