public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Carl Love <cel@linux.ibm.com>
To: Luis Machado <luis.machado@arm.com>,
	blarsen@redhat.com, Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	gdb-patches@sourceware.org
Cc: Carl Love <cel@linux.ibm.com>, Pedro Alves <pedro@palves.net>,
	Tom Tromey <tom@tromey.com>, Simon Marchi <simark@simark.ca>
Subject: [ PATCH 1/3] Fix GDB reverse execution behavior
Date: Wed, 22 Nov 2023 15:33:07 -0800	[thread overview]
Message-ID: <0743198c95396b679bd2215a6518d9e97ffa80f5.camel@linux.ibm.com> (raw)
In-Reply-To: <ee4ed81911a3196327c2aea3fa9a77f910a5e798.camel@linux.ibm.com>

GDB maintainers:

This patch in the series is unchanged from the previously posted
version 2 patch of patch 1 in the previous patch series.
 
Version 2, updated the compiler check and handling for gcc version 6
and earlier.  Retested on Power 10.

Per the comments on version 4 for the gdb.reverse/func-map-to-same-
line.exp, I have added support to proc gdb_compile to enable or disable
generating line information as part of the debug information.  The two
new options are column-info and no-column-info.  

This patch implements the new options for gdb_compile.

These options have been tested with patch 2 and patch 3 on PowerPC with
the GCC and clang compilers.

Please let me know if the patch is acceptable for mainline.   Thanks.

                   Carl

------------------------------------------------------------

Add gdb_compile options column-info and no-column-info

This patch adds two new options to gdb_compile to specify if the compile
should or should not generate the line table information.  The
options are supported on clang and gcc version 7 and newer.

Patch has been tested on PowerPC with both gcc and clang.
---
 gdb/testsuite/lib/gdb.exp | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/gdb/testsuite/lib/gdb.exp b/gdb/testsuite/lib/gdb.exp
index 63885860795..a63394d5cc0 100644
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -5150,6 +5150,8 @@ proc quote_for_host { args } {
 #     debug information
 #   - text_segment=addr: Tell the linker to place the text segment at ADDR.
 #   - build-id: Ensure the final binary includes a build-id.
+#   - column-info/no-column-info: Enable/Disable generation of column table
+#     information.
 #
 # And here are some of the not too obscure options understood by DejaGnu that
 # influence the compilation:
@@ -5359,6 +5361,38 @@ proc gdb_compile {source dest type options} {
             } else {
                 error "Don't know how to handle text_segment option."
             }
+	} elseif { $opt == "column-info" } {
+	    # If GCC or clang does not support column-info, compilation
+	    # will fail and the usupported column-info option will be
+	    # reported as such.
+	    if {[test_compiler_info {gcc-*}]} {
+		lappend new_options "additional_flags=-gcolumn-info"
+
+	    } elseif {[test_compiler_info {clang-*}]} {
+		lappend new_options "additional_flags=-gcolumn-info"
+
+	    } else {
+		error "Option gcolumn-info option not supported by compiler."
+	    }
+
+	} elseif { $opt == "no-column-info" } {
+	    if {[test_compiler_info {gcc-*}]} {
+		if {[test_compiler_info {gcc-[1-6]-*}]} {
+		    # In this case, don't add the compile line option and
+		    # the result will be the same as using no-column-info
+		    # on a version that supports the option.
+		    warning "gdb_compile option no-column-info not supported, ignoring."
+		} else {
+		    lappend new_options "additional_flags=-gno-column-info"
+		}
+
+	    } elseif {[test_compiler_info {clang-*}]} {
+		lappend new_options "additional_flags=-gno-column-info"
+
+	    } else {
+		error "Option gno-column-info option not supported by compiler."
+	    }
+
         } else {
             lappend new_options $opt
         }
-- 
2.41.0



  parent reply	other threads:[~2023-11-23  5:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f624c5566d6a8a1014ecc38900ca1ba0202989ef.camel@linux.ibm.com>
     [not found] ` <890101c23dd5fa60fcbf9d4b299cb2a533c260b7.camel@linux.ibm.com>
     [not found]   ` <1e702d8f-e5b4-4719-b1e7-42210f350305@arm.com>
     [not found]     ` <a01f4e5f3fd399e3a9a971421265b34d08e32388.camel@linux.ibm.com>
     [not found]       ` <643afce1-ab9b-4e8b-bcbb-5738dc409a28@arm.com>
     [not found]         ` <9e17008084c34f953f5318933436ec703250120a.camel@linux.ibm.com>
     [not found]           ` <92a751d1-a4b9-4c21-821e-a1dc67207516@arm.com>
     [not found]             ` <ee4ed81911a3196327c2aea3fa9a77f910a5e798.camel@linux.ibm.com>
2023-11-22 23:33               ` [ PATCH 0/3] " Carl Love
2023-11-30 11:36                 ` Guinevere Larsen
2023-11-30 15:39                   ` Carl Love
2023-11-30 15:43                     ` Luis Machado
2023-12-11 14:40                       ` Luis Machado
2023-12-14 16:10                         ` Carl Love
2024-01-02 22:52                           ` Carl Love
2023-11-30 15:45                     ` Guinevere Larsen
2023-11-22 23:33               ` Carl Love [this message]
2023-11-29 11:44                 ` [ PATCH 1/3] " Luis Machado
2023-11-29 16:30                   ` Carl Love
2023-11-29 16:38                     ` Luis Machado
2023-11-22 23:33               ` [ PATCH 2/3] " Carl Love
2023-11-29 11:44                 ` Luis Machado
2023-11-22 23:33               ` [PATCH 3/3] " Carl Love
2023-11-29 11:46                 ` Luis Machado
2023-11-29 16:30                   ` Carl Love

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=0743198c95396b679bd2215a6518d9e97ffa80f5.camel@linux.ibm.com \
    --to=cel@linux.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=blarsen@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@arm.com \
    --cc=pedro@palves.net \
    --cc=simark@simark.ca \
    --cc=tom@tromey.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).