From: Tamar Christina <Tamar.Christina@arm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: "gdb-buildbot@sergiodj.net" <gdb-buildbot@sergiodj.net>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: RE: Breakage on builder NetBSD-x86_64-m64, revision 378272cef651024de67dc0e09d3f41ae2d66f8bd [gdb-8.0-branch]
Date: Mon, 21 May 2018 14:03:00 -0000 [thread overview]
Message-ID: <HE1PR08MB0540635A14EECDB01B704216FF950@HE1PR08MB0540.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <0d85f7bfa0b398ef7ab7ca37e55f5933@polymtl.ca>
> -----Original Message-----
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Sent: Monday, May 21, 2018 14:11
> To: Tamar Christina <Tamar.Christina@arm.com>
> Cc: gdb-buildbot@sergiodj.net; gdb-patches@sourceware.org; nd
> <nd@arm.com>
> Subject: Re: Breakage on builder NetBSD-x86_64-m64, revision
> 378272cef651024de67dc0e09d3f41ae2d66f8bd [gdb-8.0-branch]
>
> On 2018-05-21 06:21, Tamar Christina wrote:
> > Hmm I don't see how my patch could have caused this, It changed only
> > one line in an aarch64 only path in a line That's IFDEF'd out by any
> > default configuration.
>
> Indeed, it's just because the 8.0 branch doesn't have this patch:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-
> gdb.git;a=commit;h=a379bfd
Ah, thanks!
Cheers,
Tamar
>
> You can safely ignore it.
>
> Simon
prev parent reply other threads:[~2018-05-21 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:07 Oh dear. I regret to inform you that commit 378272cef651024de67dc0e09d3f41ae2d66f8bd might be unfortunate [gdb-8.0-branch] gdb-buildbot
2018-05-21 10:21 ` Breakage on builder NetBSD-x86_64-m64, revision 378272cef651024de67dc0e09d3f41ae2d66f8bd [gdb-8.0-branch] gdb-buildbot
2018-05-21 11:07 ` Tamar Christina
2018-05-21 13:19 ` Simon Marchi
2018-05-21 14:03 ` Tamar Christina [this message]
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=HE1PR08MB0540635A14EECDB01B704216FF950@HE1PR08MB0540.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--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