From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Andrew Haley <aph@redhat.com>,
Tom Tromey <tromey@redhat.com>
Subject: [commit] Replace additional_flags by ldflags (was Re: [PATCH] Fix ARM sign-extension on PC when using 64-bit BFD)
Date: Mon, 22 Apr 2013 15:32:00 -0000 [thread overview]
Message-ID: <m3txmylwx7.fsf_-_@redhat.com> (raw)
In-Reply-To: <m338uior8p.fsf@redhat.com> (Sergio Durigan Junior's message of "Mon, 22 Apr 2013 06:21:26 -0300")
On Monday, April 22 2013, I wrote:
> Thanks, checked-in:
>
> http://sourceware.org/ml/gdb-cvs/2013-04/msg00213.html
Ops, what I committed was a previous version of the patch. They're
almost the same, with the difference that instead of using
"additional_flags" the new version uses "ldflags", a change suggested by
Pedro himself.
I am sorry about the confusion, it has been fixed by the patch below.
Checked-in.
Thanks,
--
Sergio
--- a/gdb/testsuite/gdb.arch/arm-bl-branch-dest.exp
+++ b/gdb/testsuite/gdb.arch/arm-bl-branch-dest.exp
@@ -26,7 +26,7 @@ standard_testfile
# the "-Wl,-Ttext-segment" option compile the binary.
if { [prepare_for_testing ${testfile}.exp ${testfile} ${srcfile} \
- [list debug additional_flags=-Wl,-Ttext-segment=0xb0000000]] } {
+ [list debug ldflags=-Wl,-Ttext-segment=0xb0000000]] } {
return -1
}
next prev parent reply other threads:[~2013-04-22 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 14:33 [PATCH] Fix ARM sign-extension on PC when using 64-bit BFD Sergio Durigan Junior
2013-04-22 13:32 ` Sergio Durigan Junior
2013-04-22 14:29 ` Pedro Alves
2013-04-22 14:46 ` Sergio Durigan Junior
2013-04-22 15:32 ` Sergio Durigan Junior [this message]
2013-04-25 17:26 ` Sergio Durigan Junior
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=m3txmylwx7.fsf_-_@redhat.com \
--to=sergiodj@redhat.com \
--cc=aph@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=tromey@redhat.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