public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/52227] New: TARGET attribute mishandled in polymorphic types Date: Mon, 13 Feb 2012 09:39:00 -0000 [thread overview] Message-ID: <bug-52227-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52227 Bug #: 52227 Summary: TARGET attribute mishandled in polymorphic types Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: missed-optimization, rejects-valid, wrong-code Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org CC: pault@gcc.gnu.org Seemingly, the TARGET attribute is mishandled. The following program gives: target :: a,b 1 Error: Duplicate TARGET attribute specified at (1) Thus, there is a rejects valid issue. However, depending which variable is declared first, there is also a potential wrong-code issue as a TARGET variable might still get the "restrict" qualifier in the gimple representation. Or a nontarget might get no "restricted", which is a missed optimization. The other attributes have to be checked as well. That includes VOLATILE and ASYNCHRONOUS. It might be enough that the variable has the proper attribute and that such the attribute is properly propagated; at least volatile seems to be handled correctly, but it should be re-checked. (Asynchronous is currently not used on gimple level, cf. PR49733/PR25829; nevertheless, it should be propagated correctly.) I think the other attributes are either related to dimension/allocatable/pointer and already taken care of - or are dummy-related attributes such as optional, value (cf. PR51284), intent etc. type t end type t class(t), allocatable :: a(:), b(:) target :: a,b select type (a) type is (t) select type (b) type is (t) a(1) = b(1) end select end select end
next reply other threads:[~2012-02-13 9:39 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-13 9:39 burnus at gcc dot gnu.org [this message] 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 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@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: linkBe 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).