Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Luis Machado (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
	Tom Tromey <tromey@sourceware.org>,
	Simon Marchi <simon.marchi@polymtl.ca>
Subject: [review] [gdb/testsuite] Compile ada with -lgnarl_pic and -lgnat_pic if required
Date: Mon, 21 Oct 2019 20:52:00 -0000	[thread overview]
Message-ID: <20191021205228.E63AD21926@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571043363000.I3e1e40bd46236b45e2d7808c1cd744a075d4a148@gnutoolchain-gerrit.osci.io>

Luis Machado has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/32
......................................................................


Patch Set 1:

(4 comments)

At first the change looked a bit too complicated for what it does. But i realized that, if we don't want to keep compiling things incorrectly over and over again, caching the setting is the only way to do it. And that makes the code a bit larger.

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/32/1/gdb/testsuite/lib/ada.exp 
File gdb/testsuite/lib/ada.exp:

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/32/1/gdb/testsuite/lib/ada.exp@16 
PS1, Line 16: # Call target_compile with SOURCE DEST TYPE and OPTIONS as argument,
            : # after having temporarily changed the current working directory to
            : # BUILDDIR.
The location of this comment needs to be adjusted, since it is now out of place.


https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/32/1/gdb/testsuite/lib/ada.exp@20 
PS1, Line 20: proc gdb_simple_compile_ada {name code {type object} {compile_flags {}} {object obj}} {
Some documentation for this function would be nice. It seems to be a helper function that returns true/false for whether a compilation succeeded or not?


https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/32/1/gdb/testsuite/lib/ada.exp@55 
PS1, Line 55: gdb_caching_proc gdb_ada_needs_libs_pic_suffix {
It would be nice to have some documentation here explaining that we're caching true/false for whether we need to use the special workaround compilation flags.


https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/32/1/gdb/testsuite/lib/ada.exp@131 
PS1, Line 131: # Compile some Ada code.
I think this is now a helper function? Should we adjust its documentation a bit?

My understanding is that gdb_compile_ada_1 now only silently tests a compilation and doesn't actually gdb_compile_test it?




       reply	other threads:[~2019-10-21 20:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gerrit.1571043363000.I3e1e40bd46236b45e2d7808c1cd744a075d4a148@gnutoolchain-gerrit.osci.io>
2019-10-21 20:52 ` Luis Machado (Code Review) [this message]
2019-10-30 16:36 ` [review v2] " Simon Marchi (Code Review)
2019-10-30 17:35 ` Tom de Vries (Code Review)
2019-10-30 17:35 ` [review v3] " Tom de Vries (Code Review)
2019-11-02  0:04 ` Joel Brobecker (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=20191021205228.E63AD21926@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@linaro.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.de \
    --cc=tromey@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