public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92793] Fortran Location Data for Diagnostic lacks the column number – when passing on to ME
Date: Fri, 30 Oct 2020 10:28:37 +0000	[thread overview]
Message-ID: <bug-92793-4-lNl4IAvJd8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92793-4@http.gcc.gnu.org/bugzilla/>

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.

       reply	other threads:[~2020-10-30 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-92793-4@http.gcc.gnu.org/bugzilla/>
2020-10-30 10:28 ` cvs-commit at gcc dot gnu.org [this message]
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

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-92793-4-lNl4IAvJd8@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).