public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52227] [OOP] TARGET attribute mishandled in polymorphic types
Date: Fri, 13 Jul 2012 15:11:00 -0000 [thread overview]
Message-ID: <bug-52227-4-bbd2x1GhTR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52227-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52227
--- Comment #3 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> 2012-07-13 15:10:52 UTC ---
Hmmm! OK - I guess that we need
class_pointer/class_target/class_allocatable attributes that are
retained by the symbol, rather than the container.
Cheers
Paul
PS I have to recover the steps between the last unlimited polymorphic
patch that I sent you and the present on, which does the job for
unlimited OOP but breaks something such that regressions run into the
hundreds. I have stared at it for a couple of evenings but cannot see
what generates the problem. If I do not see it by Sunday, I'll let
you take a look.
On 13 July 2012 15:17, burnus at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52227
>
> Tobias Burnus <burnus at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |janus at gcc dot gnu.org
>
> --- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-07-13 13:17:23 UTC ---
> I think we need so change class.c's gfc_build_class_symbol. It currently only
> handles pointer/allocatable plus a (co)rank.
>
> It seems to definitely lacks support for TARGET, judging by this PR, PR51610
> and PR53951. At least I fear that some wrong-code bug is lurking there if
> TARGET is not properly set.
>
> As written in comment 0, there might be other attributes which have to be taken
> into account, e.g. VOLATILE or ASYNCHRONUOUS.
>
> Recall that when adding letters to the type name, either the number of allowed
> characters has to change or the length part in the hashing, otherwise, names
> might get cropped.
>
> We should try to fix this issue soonish, as it is a nasty wrong-code issue
> (depending on the optimization and timing) and it affects the ABI!
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
next prev parent reply other threads:[~2012-07-13 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 9:39 [Bug fortran/52227] New: " burnus at gcc dot gnu.org
2012-02-15 21:20 ` [Bug fortran/52227] [OOP] " burnus at gcc dot gnu.org
2012-07-13 13:17 ` burnus at gcc dot gnu.org
2012-07-13 15:11 ` paul.richard.thomas at gmail dot com [this message]
2013-06-11 19:07 ` dominiq at lps dot ens.fr
2023-03-06 17:50 ` anlauf at gcc dot gnu.org
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=bug-52227-4-bbd2x1GhTR@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).