From: Harald Anlauf <anlauf@gmx.de>
To: fortran@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fortran: Mark internal symbols as artificial [PR88009,PR68800]
Date: Tue, 16 Nov 2021 21:46:32 +0100 [thread overview]
Message-ID: <c775c962-6953-faf1-7c23-72b00bc7e029@gmx.de> (raw)
In-Reply-To: <20211114231748.376086cd@nbbrfq>
Hi Bernhard,
I'm trying to understand your patch. What does it really try to solve?
PR88009 is closed and seems to have nothing to do with this.
Harald
Am 14.11.21 um 23:17 schrieb Bernhard Reutner-Fischer via Fortran:
> Hi!
>
> Amend fix for PR88009 to mark all these class components as artificial.
>
> gcc/fortran/ChangeLog:
>
> * class.c (gfc_build_class_symbol, generate_finalization_wrapper,
> (gfc_find_derived_vtab, find_intrinsic_vtab): Use stringpool for
> names. Mark internal symbols as artificial.
> * decl.c (gfc_match_decl_type_spec, gfc_match_end): Fix
> indentation.
> (gfc_match_derived_decl): Fix indentation. Check extension level
> before incrementing refs counter.
> * parse.c (parse_derived): Fix style.
> * resolve.c (resolve_global_procedure): Likewise.
> * symbol.c (gfc_check_conflict): Do not ignore artificial symbols.
> (gfc_add_flavor): Reorder condition, cheapest first.
> (gfc_new_symbol, gfc_get_sym_tree,
> generate_isocbinding_symbol): Fix style.
> * trans-expr.c (gfc_trans_subcomponent_assign): Remove
> restriction on !artificial.
> * match.c (gfc_match_equivalence): Special-case CLASS_DATA for
> warnings.
>
> ---
> gfc_match_equivalence(), too, should not bail-out early on the first
> error but should diagnose all errors. I.e. not goto cleanup but set
> err=true and continue in order to diagnose all constraints of a
> statement. Maybe Sandra or somebody else will eventually find time to
> tweak that.
>
> I think it also plugs a very minor leak of name in gfc_find_derived_vtab
> so i also tagged it [PR68800]. At least that was the initial
> motiviation to look at that spot.
> We were doing
> - name = xasprintf ("__vtab_%s", tname);
> ...
> gfc_set_sym_referenced (vtab);
> - name = xasprintf ("__vtype_%s", tname);
>
> Bootstrapped and regtested without regressions on x86_64-unknown-linux.
> Ok for trunk?
>
next prev parent reply other threads:[~2021-11-16 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 22:17 Bernhard Reutner-Fischer
2021-11-16 20:46 ` Harald Anlauf [this message]
2021-11-17 8:12 ` Bernhard Reutner-Fischer
2021-11-17 20:32 ` Harald Anlauf
2024-01-29 20:45 ` Bernhard Reutner-Fischer
2024-01-29 21:06 ` Harald Anlauf
2024-01-29 22:18 ` rep.dot.nop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c775c962-6953-faf1-7c23-72b00bc7e029@gmx.de \
--to=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).