public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
@ 2020-10-30 10:28 ` cvs-commit at gcc dot gnu.org
2020-10-30 10:29 ` cvs-commit at gcc dot gnu.org
` (4 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-10-30 10:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:fa410314ec94c9df2ad270c1917adc51f9147c2c
commit r11-4567-gfa410314ec94c9df2ad270c1917adc51f9147c2c
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Thu Oct 29 16:12:38 2020 +0100
[OpenACC] Elaborate testcases that verify column location information
[PR92793]
After PR92793 commit 9c81750c5bedd7883182ee2684a012c6210ebe1d "Fortran] PR
92793 - fix column used for error diagnostic", commit
d0d0ba20f2345023e9cec2419c9fb9e6cc7098c6 did "Add tests to verify OpenACC
clause locations", later fixed up in PR92901 commit
e6c90dba73291435c244decb9a89c47019cc5a45 to "Fix PR92901: Change test
expectation for C++ in OpenACC test clause-locations.c".
Now, add some more testing to verify/document the status quo.
gcc/testsuite/
PR fortran/92793
* c-c++-common/goacc/clause-locations.c: Rewrite into...
* c-c++-common/goacc/pr92793-1.c: ... this.
* gfortran.dg/goacc/clause-locations.f90: Rewrite into...
* gfortran.dg/goacc/pr92793-1.f90: ... this.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
2020-10-30 10:28 ` [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME cvs-commit at gcc dot gnu.org
@ 2020-10-30 10:29 ` cvs-commit at gcc dot gnu.org
2020-11-02 13:26 ` cvs-commit at gcc dot gnu.org
` (3 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-10-30 10:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Thomas Schwinge
<tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:fc423b4e5b16dc02cc9f91fdfc800d00a5103dea
commit r10-8956-gfc423b4e5b16dc02cc9f91fdfc800d00a5103dea
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Thu Oct 29 16:12:38 2020 +0100
[OpenACC] Elaborate testcases that verify column location information
[PR92793]
After PR92793 commit 9c81750c5bedd7883182ee2684a012c6210ebe1d "Fortran] PR
92793 - fix column used for error diagnostic", commit
d0d0ba20f2345023e9cec2419c9fb9e6cc7098c6 did "Add tests to verify OpenACC
clause locations", later fixed up in PR92901 commit
e6c90dba73291435c244decb9a89c47019cc5a45 to "Fix PR92901: Change test
expectation for C++ in OpenACC test clause-locations.c".
Now, add some more testing to verify/document the status quo.
gcc/testsuite/
PR fortran/92793
* c-c++-common/goacc/clause-locations.c: Rewrite into...
* c-c++-common/goacc/pr92793-1.c: ... this.
* gfortran.dg/goacc/clause-locations.f90: Rewrite into...
* gfortran.dg/goacc/pr92793-1.f90: ... this.
(cherry picked from commit fa410314ec94c9df2ad270c1917adc51f9147c2c)
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
2020-10-30 10:28 ` [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME cvs-commit at gcc dot gnu.org
2020-10-30 10:29 ` cvs-commit at gcc dot gnu.org
@ 2020-11-02 13:26 ` cvs-commit at gcc dot gnu.org
2020-11-02 13:28 ` cvs-commit at gcc dot gnu.org
` (2 subsequent siblings)
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-02 13:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:5677444f7e7ca15557030902c3d09dab4852fa90
commit r11-4608-g5677444f7e7ca15557030902c3d09dab4852fa90
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Fri Oct 30 13:13:51 2020 +0100
Further improve Fortran column location information [PR92793]
Building on top of commit 9c81750c5bedd7883182ee2684a012c6210ebe1d
"Fortran] PR
92793 - fix column used for error diagnostic", there is another place where
we
have to use 'gfc_get_location' returning column-corrected locations.
For example, this improves column location information for OMP constructs.
gcc/fortran/
PR fortran/92793
* trans.c (gfc_set_backend_locus): Use 'gfc_get_location'.
(gfc_restore_backend_locus): Adjust.
gcc/testsuite/
PR fortran/92793
* gfortran.dg/goacc/pr92793-1.f90: Adjust.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2020-11-02 13:26 ` cvs-commit at gcc dot gnu.org
@ 2020-11-02 13:28 ` cvs-commit at gcc dot gnu.org
2020-11-03 8:14 ` cvs-commit at gcc dot gnu.org
2020-11-03 8:15 ` cvs-commit at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-02 13:28 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Thomas Schwinge
<tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:a5c5f9e181c1f7548930f1cab91002b9d460cc92
commit r10-8960-ga5c5f9e181c1f7548930f1cab91002b9d460cc92
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Fri Oct 30 13:13:51 2020 +0100
Further improve Fortran column location information [PR92793]
Building on top of commit 9c81750c5bedd7883182ee2684a012c6210ebe1d
"Fortran] PR
92793 - fix column used for error diagnostic", there is another place where
we
have to use 'gfc_get_location' returning column-corrected locations.
For example, this improves column location information for OMP constructs.
gcc/fortran/
PR fortran/92793
* trans.c (gfc_set_backend_locus): Use 'gfc_get_location'.
(gfc_restore_backend_locus): Adjust.
gcc/testsuite/
PR fortran/92793
* gfortran.dg/goacc/pr92793-1.f90: Adjust.
(cherry picked from commit 5677444f7e7ca15557030902c3d09dab4852fa90)
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
` (3 preceding siblings ...)
2020-11-02 13:28 ` cvs-commit at gcc dot gnu.org
@ 2020-11-03 8:14 ` cvs-commit at gcc dot gnu.org
2020-11-03 8:15 ` cvs-commit at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-03 8:14 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas Schwinge <tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:41f7f6178e2d35288273656dc55dae8fcf3edeb5
commit r11-4639-g41f7f6178e2d35288273656dc55dae8fcf3edeb5
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Tue Oct 27 17:14:10 2020 +0100
[Fortran] More precise location information for OpenACC 'gang', 'worker',
'vector' clauses with argument [PR92793]
gcc/fortran/
PR fortran/92793
* trans-openmp.c (gfc_trans_omp_clauses): More precise location
information for OpenACC 'gang', 'worker', 'vector' clauses with
argument.
gcc/testsuite/
PR fortran/92793
* gfortran.dg/goacc/pr92793-1.f90: Adjust.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
` (4 preceding siblings ...)
2020-11-03 8:14 ` cvs-commit at gcc dot gnu.org
@ 2020-11-03 8:15 ` cvs-commit at gcc dot gnu.org
5 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2020-11-03 8:15 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92793
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Thomas Schwinge
<tschwinge@gcc.gnu.org>:
https://gcc.gnu.org/g:5ceaf8a54abb3f9bd3c268fe420999a7962b2a15
commit r10-8965-g5ceaf8a54abb3f9bd3c268fe420999a7962b2a15
Author: Thomas Schwinge <thomas@codesourcery.com>
Date: Tue Oct 27 17:14:10 2020 +0100
[Fortran] More precise location information for OpenACC 'gang', 'worker',
'vector' clauses with argument [PR92793]
gcc/fortran/
PR fortran/92793
* trans-openmp.c (gfc_trans_omp_clauses): More precise location
information for OpenACC 'gang', 'worker', 'vector' clauses with
argument.
gcc/testsuite/
PR fortran/92793
* gfortran.dg/goacc/pr92793-1.f90: Adjust.
(cherry picked from commit 41f7f6178e2d35288273656dc55dae8fcf3edeb5)
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-11-03 8:15 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
2020-10-30 10:28 ` [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME cvs-commit at gcc dot gnu.org
2020-10-30 10:29 ` cvs-commit at gcc dot gnu.org
2020-11-02 13:26 ` cvs-commit at gcc dot gnu.org
2020-11-02 13:28 ` cvs-commit at gcc dot gnu.org
2020-11-03 8:14 ` cvs-commit at gcc dot gnu.org
2020-11-03 8:15 ` cvs-commit 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).