From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>, Yao Qi <yao.qi@linaro.org>
Subject: Re: [PATCH] Fix build breakage on GNU/Linux AArch64 and use std::vector on tdesc.reg_defs
Date: Sun, 10 Sep 2017 09:03:00 -0000 [thread overview]
Message-ID: <41ee3f9801392370c02481e2f77aa8dc@polymtl.ca> (raw)
In-Reply-To: <20170910055056.21186-1-sergiodj@redhat.com>
On 2017-09-10 07:50, Sergio Durigan Junior wrote:
> This patch fixes the build breakage that has been happening on AArch64
> since September 5th. The breakage was introduced by the following
> commit:
>
> author Yao Qi <yao.qi@linaro.org>
> Tue, 5 Sep 2017 04:54:52 -0400 (09:54 +0100)
> committer Yao Qi <yao.qi@linaro.org>
> Tue, 5 Sep 2017 04:54:52 -0400 (09:54 +0100)
> commit f7000548a2b79d7e5cb924468117ca4245e6b820
>
> Use VEC for target_desc.reg_defs
>
> The build log for this commit can be seen here:
>
>
> <https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64/builds/2696/steps/compile%20gdb/logs/stdio>
>
> And the underlying problem is that the code is not calling the new
> function "allocate_target_description" to allocate the "struct
> target_desc" using "new" instead of XNEW, which end up not properly
> initializing the fields of the structure.
>
> I took the opportunity to convert the code to std::vector (instead of
> VEC), which makes things even simpler. This has been regtested on the
> BuildBot, without regressions, and fixes the build breakage.
Hi Sergio,
This patch seems to do two independent changes:
- use allocate_target_description instead of XNEW
- replace VEC with std::vector
Can you post separate patches? You can push the first one directly, I
would call it obvious (and it's the important bits to fix the build).
The second one, Yao might want to take a look.
Thanks!
Simon
next prev parent reply other threads:[~2017-09-10 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-10 5:52 Sergio Durigan Junior
2017-09-10 9:03 ` Simon Marchi [this message]
2017-09-10 16:12 ` 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=41ee3f9801392370c02481e2f77aa8dc@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
--cc=yao.qi@linaro.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