public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Nils-Christian Kempke <nils-christian.kempke@intel.com>
To: gdb-patches@sourceware.org
Cc: brobecker@adacore.com,
	Nils-Christian Kempke <nils-christian.kempke@intel.com>
Subject: [PATCH v2 0/1] gdb, testsuite, fortran: adapt info symbol expected output for intel compilers
Date: Mon, 17 Jan 2022 12:30:04 +0100	[thread overview]
Message-ID: <20220117113005.3867815-1-nils-christian.kempke@intel.com> (raw)

This is version two of a patch that I first had sent to as a RFC

  https://sourceware.org/pipermail/gdb-patches/2022-January/184776.html

There were only two changes: first, since 

  2026dcfcc0c0e60efa968b889f010a10a93cfe09

has been pushed recently, I added ifx as an exception to the test
as well.  Second, I incorporated the encode/decode terminology when
talking about Ada.

Cheers,
Nils

Nils-Christian Kempke (1):
  gdb, testsuite, fortran: adapt info symbol expected output intel
    compilers

 gdb/testsuite/gdb.fortran/nested-funcs-2.exp | 29 ++++++++++++++++++--
 1 file changed, 27 insertions(+), 2 deletions(-)

-- 
2.25.1

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva  
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


             reply	other threads:[~2022-01-17 11:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 11:30 Nils-Christian Kempke [this message]
2022-01-17 11:30 ` [PATCH v2 1/1] " Nils-Christian Kempke
2022-01-21 16:49   ` Andrew Burgess
2022-01-23 10:05     ` Joel Brobecker
2022-01-25  7:45       ` Kempke, Nils-Christian
2022-01-28 18:24         ` Tom Tromey

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=20220117113005.3867815-1-nils-christian.kempke@intel.com \
    --to=nils-christian.kempke@intel.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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).