public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: "Kempke, Nils-Christian" <nils-christian.kempke@intel.com>
Cc: gdb-patches@sourceware.org, "Potharla,
	Rupesh" <Rupesh.Potharla@amd.com>,
	"George, Jini Susan" <JiniSusan.George@amd.com>,
	"Parasuraman, Hariharan" <Hariharan.Parasuraman@amd.com>,
	"Sharma, Alok Kumar" <AlokKumar.Sharma@amd.com>
Subject: Re: GDB/Fortran: Support for Assumed Rank Zero.
Date: Wed, 20 Apr 2022 08:38:21 -0700	[thread overview]
Message-ID: <20220420083821.21925246@f35-zws-1> (raw)
In-Reply-To: <CY4PR1101MB2071BBFECC39AA152CE69F58B8F59@CY4PR1101MB2071.namprd11.prod.outlook.com>

On Wed, 20 Apr 2022 06:32:25 +0000
"Kempke, Nils-Christian" <nils-christian.kempke@intel.com> wrote:

> But running
>    make check TESTS="gdb.fortran/assumedrank.exp" RUNTESTFLAGS="F90_FOR_TARGET=flang"
> and looking at the log will show that the compiler identification actually identified
> gcc and gfortran as the compiler used (it will still try to compile with flang but the identified
> compiler in get_/test_compiler_info is gcc..). From my run in gdb.log:
> 
>    get_compiler_info: gcc-9-3-0
>    UNTESTED: gdb.fortran/assumedrank.exp: compiler does not support assumed rank
>    testcase /.../gdb/testsuite/gdb.fortran/assumedrank.exp completed in 0 seconds
> 
>                    === gdb Summary ===
> 
>    # of untested testcases         1
> 
> The correct command would probably be
> 
>    make check TESTS="gdb.fortran/assumedrank.exp" RUNTESTFLAGS="F90_FOR_TARGET=flang
>       CC_FOR_TARGET=clang"
> 
> which leads to output like:
> 
>    Running .../testsuite/gdb.fortran/pointers.exp ...
>    get_compiler_info: clang-10-0-0

Thanks for this info.  I do indeed see similar results when setting both
F90_FOR_TARGET and CC_FOR_TARGET.

Kevin


  reply	other threads:[~2022-04-20 15:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13  9:55 Potharla, Rupesh
2022-04-13 18:27 ` Kevin Buettner
2022-04-14 10:30   ` Potharla, Rupesh
2022-04-14 21:28     ` Kevin Buettner
2022-04-15 13:33       ` Potharla, Rupesh
2022-04-15 19:31         ` Kevin Buettner
2022-04-16 18:29           ` Potharla, Rupesh
2022-04-18 13:31             ` Tom Tromey
2022-04-18 15:25               ` Potharla, Rupesh
2022-04-20 15:22                 ` Andrew Burgess
2022-04-20 19:08                   ` Potharla, Rupesh
2022-04-22 14:38                     ` Andrew Burgess
2022-04-25  6:33                       ` Potharla, Rupesh
2022-04-25  8:47                         ` Andrew Burgess
2022-04-18 15:33             ` Kevin Buettner
2022-04-19 17:30               ` Kevin Buettner
2022-04-20  0:29                 ` Potharla, Rupesh
2022-04-20  6:32                   ` Kempke, Nils-Christian
2022-04-20 15:38                     ` Kevin Buettner [this message]
2022-04-20 15:29                   ` Andrew Burgess
2022-04-20 19:20                     ` Potharla, Rupesh

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=20220420083821.21925246@f35-zws-1 \
    --to=kevinb@redhat.com \
    --cc=AlokKumar.Sharma@amd.com \
    --cc=Hariharan.Parasuraman@amd.com \
    --cc=JiniSusan.George@amd.com \
    --cc=Rupesh.Potharla@amd.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nils-christian.kempke@intel.com \
    /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).