From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH,v2] [sim] Fix build failure in d10v sim
Date: Wed, 12 May 2021 00:59:04 -0300 [thread overview]
Message-ID: <cee4c829-6512-5546-b9e7-0e940e76e1f2@linaro.org> (raw)
In-Reply-To: <YJr9LgS7xHF+XB9g@vapier>
On 5/11/21 6:54 PM, Mike Frysinger wrote:
> On 11 May 2021 10:07, Luis Machado wrote:
>> + /* Make sure we have the right structure for the following memset. */
>> + _Static_assert ((uintptr_t) &State == (uintptr_t) &State.regs,
>> + "&State != &State.regs");
>
> we require C11, so you can include assert.h & use static_assert().
> -mike
>
Pushed with that change. Thanks!
prev parent reply other threads:[~2021-05-12 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 19:14 [PATCH] " Luis Machado via Gdb-patches
2021-05-10 22:30 ` Mike Frysinger via Gdb-patches
2021-05-11 2:01 ` Luis Machado via Gdb-patches
2021-05-11 20:48 ` Mike Frysinger via Gdb-patches
2021-05-11 13:07 ` [PATCH,v2] " Luis Machado via Gdb-patches
2021-05-11 21:54 ` Mike Frysinger via Gdb-patches
2021-05-12 3:59 ` Luis Machado via Gdb-patches [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=cee4c829-6512-5546-b9e7-0e940e76e1f2@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=luis.machado@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