From: Nick Alcock <nick.alcock@oracle.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Simon Marchi <simark@simark.ca>,
gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org,
binutils@sourceware.org,
"Jose E. Marchesi" <jose.marchesi@oracle.com>
Subject: Re: [PATCH] Fix a number of build problems found on Solaris and NetBSD (was Re: Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate)
Date: Wed, 29 May 2019 20:08:00 -0000 [thread overview]
Message-ID: <87h89d3tyf.fsf@esperi.org.uk> (raw)
In-Reply-To: <ydd5zptglyq.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Wed, 29 May 2019 20:22:05 +0200")
On 29 May 2019, Rainer Orth outgrape:
> I've just tried a build of the gdb side of binutils-gdb with your patch
> applied on amd64-pc-solaris2.11 for good measure: worked just fine
> without any warnings.
Great news!
(This is quite irrelevant since we're not currently caring about ABI/API
stability for libctf, but it doesn't change the API or ABI on 64-bit
systems either, since no type will have an ID remotely near the 63-bit
sign-bit boundary: the max is currently 2^32-2.)
next prev parent reply other threads:[~2019-05-29 20:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 0:02 Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate gdb-buildbot
2019-05-29 0:02 ` Breakage on builder Solaris11-sparcv9-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d gdb-buildbot
2019-05-29 1:34 ` Breakage on builder Solaris11-amd64-m64, " gdb-buildbot
2019-05-29 2:16 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Simon Marchi
2019-05-29 10:21 ` Rainer Orth
2019-05-29 12:46 ` Nix
2019-05-29 13:14 ` Andreas Schwab
2019-05-29 13:38 ` Rainer Orth
2019-05-29 14:18 ` Nick Alcock
2019-05-29 16:33 ` [PATCH] Fix a number of build problems found on Solaris and NetBSD (was Re: Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate) Nick Alcock
2019-05-29 18:22 ` Rainer Orth
2019-05-29 20:08 ` Nick Alcock [this message]
2019-05-29 20:34 ` Kamil Rytarowski
2019-05-29 21:46 ` Nick Alcock
2019-05-30 0:54 ` Sergio Durigan Junior
2019-05-30 7:14 ` Kamil Rytarowski
2019-05-30 9:35 ` Nick Alcock
2019-05-29 16:04 ` Oh dear. I regret to inform you that commit 0e65dfbaf3a0299e4837216a103c28625d4b4f1d might be unfortunate Nick Alcock
2019-05-29 4:26 ` Breakage on builder NetBSD-x86_64-m64, revision 0e65dfbaf3a0299e4837216a103c28625d4b4f1d gdb-buildbot
2019-05-29 5:51 ` Kamil Rytarowski
2019-05-29 12:51 ` Nick Alcock
2019-05-29 23:31 ` Breakage on builder Fedora-x86_64-w64-mingw32, " gdb-buildbot
2019-05-30 0:13 ` Nick Alcock
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=87h89d3tyf.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=simark@simark.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