Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: Luis Machado <luis.machado@linaro.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Skip VLA structure field tests when compiling with clang
Date: Fri, 10 Jul 2020 13:00:19 +0100	[thread overview]
Message-ID: <20200710120019.GA3062@blade.nx> (raw)
In-Reply-To: <f710505e-18d9-e3a3-dc74-9d828d7a0750@linaro.org>

Luis Machado wrote:
> Hi Gary,
> 
> On 7/8/20 12:46 PM, Gary Benson wrote:
> > Hi Luis,
> > 
> > Luis Machado wrote:
> > > As a general comment (for this and other patches like this), I
> > > think the preprocessor blocks intermixed with the test code make
> > > it harder to follow and update the test.
> > > 
> > > If clang claims it will never support a particular feature, then
> > > maybe we should ... separate the bits clang doesn't support and
> > > put it into a separate test that clang-compiled hosts should
> > > skip?
> > 
> > Thanks for the review.  I've made that change, the updated patch
> > is below.  I checked it on Fedora 31 x86_64, GCC and clang.  Is it
> > ok to commit?
> 
> Thanks. That looks cleaner. Just a gotcha below...
> 
[snip]
> > +
> > +# Clang says it will never support variable length arrays in structures.
> > +if {[test_compiler_info clang*]} {
> > +    unsupported "compiler does not variable length arrays in structure"
> 
>                                       ^^^ support?
> 
> Otherwise this looks good to me. Can't approve a commit though.

Good catch.  Thanks for your review, I've fixed this in my tree.

Cheers,
Gary

-- 
Gary Benson - he / him / his
Principal Software Engineer, Red Hat



  reply	other threads:[~2020-07-10 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 11:12 [PATCH] " Gary Benson
2020-06-30 17:25 ` Luis Machado
2020-07-08 15:46   ` [PATCH v2] " Gary Benson
2020-07-09 16:44     ` Luis Machado
2020-07-10 12:00       ` Gary Benson [this message]
2020-07-10 14:31         ` Pedro Alves
2020-07-13 13:49           ` Gary Benson

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=20200710120019.GA3062@blade.nx \
    --to=gbenson@redhat.com \
    --cc=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