* OpenACC regression and development pace
@ 2019-12-20 14:34 Thomas Koenig
0 siblings, 0 replies; only message in thread
From: Thomas Koenig @ 2019-12-20 14:34 UTC (permalink / raw)
To: fortran, gcc mailing list, gcc-patches
Hi, I just saw this:
FAIL: gfortran.dg/goacc/finalize-1.f -O scan-tree-dump-times gimple
"(?n)#pragma omp target oacc_enter_exit_data
map\\(delete:MEM\\[\\(c_char \\*\\)[^\\]]+\\] \\[len: [^\\]]+\\]\\)
map\\(to:del_f_p \\[pointer set, len: [0-9]+\\]\\)
map\\(alloc:del_f_p\\.data \\[pointer assign, bias: [^\\]]+\\]\\)
finalize$" 1
FAIL: gfortran.dg/goacc/finalize-1.f -O scan-tree-dump-times gimple
"(?n)#pragma omp target oacc_enter_exit_data
map\\(force_from:MEM\\[\\(c_char \\*\\)[^\\]]+\\] \\[len: [^\\]]+\\]\\)
map\\(to:cpo_f_p \\[pointer set, len: [0-9]+\\]\\)
map\\(alloc:cpo_f_p\\.data \\[pointer assign, bias: [^\\]]+\\]\\)
finalize$" 1
Regarding what is currently going on with OpenACC: I do not claim to
understand this area of the compiler, but it certainly seems that the
current development is too hasty - too many patches flying around,
too many regressions occurring. It might be better to slow this
down somewhat, and to conduct a more throrough review process before
committing.
Regards
Thomas
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-20 14:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-20 14:34 OpenACC regression and development pace Thomas Koenig
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).