Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Blaikie <dblaikie@gmail.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: [patch] [gdb/testsuite] include a use of the definition of a type to cause clang to emit debug info
Date: Sun, 13 Apr 2014 06:43:00 -0000	[thread overview]
Message-ID: <CAENS6EvK8+AUQrj_0q2vAz0JH-5Pt0Z=cRWtW--4pyyUTP3WfQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]

Clang has an optimization that causes a the debug info to only include
the declaration of a type if the type is referenced but never used in
a context that requires a definition (eg: pointers are handed around
but never deferenced).

This patch introduces a variable to one test file to cause clang to
emit the full definition of the type as well as fixing up a related
typo in the test message of the associated expect file.

Like the difference between GCC and Clang in the emission of unused
static entities, I think this case is also a matter of degrees - both
GCC and Clang implement other similar optimizations* to the one
outlined here and the GDB test suite has managed to pass without
disabling those optimizations in GCC and I hope it's suitable to do
the same for Clang.

Though admittedly I don't have much of the context of the history of
the testsuite, its priorities/preferences when it comes to
distinguishing testing compiler behavior versus debugger behavior,
etc.

* the one I know of involves dynamic types: both GCC and Clang only
emit the debug info definition of such a type in any translation unit
that emits the key function. This means in many contexts where a full
definition is provided in the source only a declaration is provided in
the debug info.

[-- Attachment #2: clang_full_type.diff --]
[-- Type: text/plain, Size: 2354 bytes --]

commit 1128f6fb45483d45668d09e0696f4a590334e0c4
Author: David Blaikie <dblaikie@gmail.com>
Date:   Sat Apr 12 23:27:19 2014 -0700

    Cause clang to emit the definition of a type used only by pointer
    
    gdb/testsuite/
    	* gdb.stabs/gdb11479.c: introduce a variable to cause clang to
    	emit the full definition of type required by the test
    	* gdb.stabs/gdb11479.exp: correct a typo in a test message

diff --git gdb/testsuite/ChangeLog gdb/testsuite/ChangeLog
index 730c116..07ba18e 100644
--- gdb/testsuite/ChangeLog
+++ gdb/testsuite/ChangeLog
@@ -1,3 +1,9 @@
+2014-04-12  David Blaikie  <dblaikie@gmail.com>
+
+        * gdb.stabs/gdb11479.c: introduce a variable to cause clang to
+	emit the full definition of type required by the test
+        * gdb.stabs/gdb11479.exp: correct a typo in a test message
+
 2014-04-12  Siva Chandra Reddy  <sivachandra@google.com>
 	    Doug Evans  <xdje42@gmail.com>
 
diff --git gdb/testsuite/gdb.stabs/gdb11479.c gdb/testsuite/gdb.stabs/gdb11479.c
index eb7fcf9..f70930f 100644
--- gdb/testsuite/gdb.stabs/gdb11479.c
+++ gdb/testsuite/gdb.stabs/gdb11479.c
@@ -55,7 +55,7 @@ struct dummy {
 enum dummy_enum {
   enum1,
   enum2
-};
+} tag_dummy_enum;
 
 void *
 hack (const struct dummy *t, const enum dummy_enum *e)
diff --git gdb/testsuite/gdb.stabs/gdb11479.exp gdb/testsuite/gdb.stabs/gdb11479.exp
index b9ed238..a2782ac 100644
--- gdb/testsuite/gdb.stabs/gdb11479.exp
+++ gdb/testsuite/gdb.stabs/gdb11479.exp
@@ -31,13 +31,13 @@ proc do_test {version} {
     gdb_test "print *t" ".*\{x = 5, y = 25, b = 2.5\}.*" \
 	"Inspect t in test2 $version"
     # Check that the enum type length has been set to a non-zero value
-    gdb_test "print sizeof (*e)" "= \[1-9\]*" "sizeof (e) in test2 $version"
+    gdb_test "print sizeof (*e)" "= \[1-9\]*" "sizeof (*e) in test2 $version"
     gdb_test "continue" "Breakpoint .* test .*" \
 	"Stop at first breakpoint $version"
     gdb_test "print *t" ".*\{x = 5, y = 25, b = 2.5\}.*" \
 	"Inspect t in test $version"
     # Check that the enum type length has been set to a non-zero value
-    gdb_test "print sizeof (*e)" "= \[1-9\]*" "sizeof (e) in test $version"
+    gdb_test "print sizeof (*e)" "= \[1-9\]*" "sizeof (*e) in test $version"
 }
 
 if { [prepare_for_testing $testfile.exp $testfile $testfile.c {debug additional_flags=-gstabs}] == 0 } {

             reply	other threads:[~2014-04-13  6:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13  6:43 David Blaikie [this message]
2014-04-13  7:52 ` David Blaikie
2014-04-23 23:04   ` Doug Evans
2014-04-14 13:10 ` Joel Brobecker
2014-04-14 15:53   ` Eric Christopher
2014-04-14 18:16     ` Joel Brobecker
2014-04-14 18:35       ` David Blaikie
2014-04-14 22:47         ` Joel Brobecker
2014-04-23 23:46           ` Pedro Alves
2014-04-24  0:20 ` Doug Evans
2014-04-24  0:29   ` Doug Evans
2014-04-24 12:36     ` Joel Brobecker
2014-04-25  5:32     ` David Blaikie

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='CAENS6EvK8+AUQrj_0q2vAz0JH-5Pt0Z=cRWtW--4pyyUTP3WfQ@mail.gmail.com' \
    --to=dblaikie@gmail.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