From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: gdb-patches@sourceware.org
Cc: Simon Marchi <simon.marchi@polymtl.ca>
Subject: [review] Add scalar_storage_order support for floating point
Date: Tue, 03 Dec 2019 21:30:00 -0000 [thread overview]
Message-ID: <20191203213036.65F532816F@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1574880479000.Ic02eb711d80ce678ef0ecf8c506a626e441b8440@gnutoolchain-gerrit.osci.io>
Tom Tromey has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/727
......................................................................
Patch Set 1:
(1 comment)
| --- gdb/testsuite/gdb.base/endianity.exp
| +++ gdb/testsuite/gdb.base/endianity.exp
| @@ -25,16 +25,17 @@ if ![runto "endianity.c:$bp_location" ] then {
| return -1
| }
|
| -gdb_test "print o" "= {v = 3, w = 2}" "print o before assignment"
| +gdb_test "print o" "= {v = 3, w = 2, f = 23.5, cplx = 1.25 \\+ 7.25 \\* I}" \
| + "print o before assignment"
|
| gdb_test "print o.v = 4" "= 4"
| gdb_test "print o.w = 3" "= 3"
| +gdb_test "print o.f = 1.5" "= 1.5"
PS1, Line 33:
> Just wondering why we don't set cplx, does gdb not offer a way to set complex?
I don't think there's a way. I went through the GCC node about
complex
types, and basically gdb doesn't implement any of it, and in fact
the way gdb print complex numbers for C is not a way that GCC can
read.
|
| # scalar_storage_order requires gcc >= 6
| if { ([test_compiler_info {gcc-[0-5]-*}] || ![test_compiler_info gcc*]) } {
| setup_xfail "*-*-*"
| }
| gdb_test "x/x &o.v" "0x04000000"
| gdb_test "x/xh &o.w" "0x0300"
|
| -gdb_test "print o" "= {v = 4, w = 3}" "print o after assignment"
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Ic02eb711d80ce678ef0ecf8c506a626e441b8440
Gerrit-Change-Number: 727
Gerrit-PatchSet: 1
Gerrit-Owner: Tom Tromey <tromey@sourceware.org>
Gerrit-Reviewer: Tom Tromey <tromey@sourceware.org>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Tue, 03 Dec 2019 21:30:35 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-12-03 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 18:48 Tom Tromey (Code Review)
2019-11-27 22:02 ` Simon Marchi (Code Review)
2019-12-03 21:30 ` Tom Tromey (Code Review) [this message]
2019-12-04 14:36 ` [review v2] " Tom Tromey (Code Review)
2019-12-04 15:33 ` Simon Marchi (Code Review)
2019-12-04 16:41 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-12-04 16:41 ` Sourceware to Gerrit sync (Code Review)
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=20191203213036.65F532816F@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
--cc=simon.marchi@polymtl.ca \
/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