public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/98009] New: [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec' should consider 'flag_openacc' in addition to 'flag_openmp'?
@ 2020-11-26 10:50 tschwinge at gcc dot gnu.org
2020-11-26 11:05 ` [Bug fortran/98009] " burnus at gcc dot gnu.org
2020-11-26 11:17 ` burnus at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2020-11-26 10:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98009
Bug ID: 98009
Summary: [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec'
should consider 'flag_openacc' in addition to
'flag_openmp'?
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: openacc
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: burnus at gcc dot gnu.org, jakub at gcc dot gnu.org
Target Milestone: ---
'gcc/fortran/match.c:gfc_match_type_spec':
/* Found leading colon in REAL::, a trailing ')' in for example
TYPE IS (REAL), or REAL, for an OpenMP list-item. */
if (c == ':' || c == ')' || (flag_openmp && c == ','))
return MATCH_YES;
If that indeed doesn't apply to OpenACC, too, then let's please add some "dummy
handling" to make this explicit, to show that we did consider this.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/98009] [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec' should consider 'flag_openacc' in addition to 'flag_openmp'?
2020-11-26 10:50 [Bug fortran/98009] New: [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec' should consider 'flag_openacc' in addition to 'flag_openmp'? tschwinge at gcc dot gnu.org
@ 2020-11-26 11:05 ` burnus at gcc dot gnu.org
2020-11-26 11:17 ` burnus at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: burnus at gcc dot gnu.org @ 2020-11-26 11:05 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98009
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I am not aware of any OpenACC construct which contains a typespec like
'INTEGER' or 'TYPE(t)'
In OpenACC it is used for gfc_match_omp_declare_reduction like is:
!$omp declare reduction (baz : integer : sub6 (omp_out, omp_in)) &
Given that specific use and syntax I am against adding a dummy entry.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug fortran/98009] [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec' should consider 'flag_openacc' in addition to 'flag_openmp'?
2020-11-26 10:50 [Bug fortran/98009] New: [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec' should consider 'flag_openacc' in addition to 'flag_openmp'? tschwinge at gcc dot gnu.org
2020-11-26 11:05 ` [Bug fortran/98009] " burnus at gcc dot gnu.org
@ 2020-11-26 11:17 ` burnus at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: burnus at gcc dot gnu.org @ 2020-11-26 11:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98009
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
→ WONTFIX for the reasons given in previous comment.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-11-26 11:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-26 10:50 [Bug fortran/98009] New: [OpenACC] 'gcc/fortran/match.c:gfc_match_type_spec' should consider 'flag_openacc' in addition to 'flag_openmp'? tschwinge at gcc dot gnu.org
2020-11-26 11:05 ` [Bug fortran/98009] " burnus at gcc dot gnu.org
2020-11-26 11:17 ` burnus at gcc dot gnu.org
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).