From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.arch/i386-avx.exp with clang
Date: Fri, 5 Nov 2021 13:20:45 +0000 [thread overview]
Message-ID: <a687a8a2-3f53-739c-a022-bc2029bb1d04@palves.net> (raw)
In-Reply-To: <1f6ed2db-5d31-9338-226e-3e1a5a7c225b@suse.de>
On 2021-11-05 13:15, Tom de Vries wrote:
> On 11/5/21 1:55 PM, Pedro Alves wrote:
>> On 2021-11-05 12:23, Tom de Vries via Gdb-patches wrote:
>>
>>>> No, but in gdb/testsuite/lib/attribute.h we do setup a compatibility
>>>> macro for 'noclone', so there's definitely precedent for using
>>>> attributes that might not be supported everywhere.
>>>>
>>>
>>> Right, I'm aware of this, but that's a typical case where we have no
>>> portable alternative.
>>
>> We actually do -- _Alignas is standard C11. This fixes the test as well:
>>
>> _Alignas(32) v8sf_t data[] =
>>
>
> I was referring to the noclone, but ok, I was not aware of the _Alignas,
> good to know, thanks.
>
> Anyway, in the latest version this is not relevant anymore, since the
> precise alignment implementation has an extra benefit, as explained in
> the post.
>
OOC, is that benefit important here?
next prev parent reply other threads:[~2021-11-05 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 13:55 Tom de Vries
2021-11-05 9:33 ` Andrew Burgess
2021-11-05 9:43 ` Tom de Vries
2021-11-05 11:54 ` Andrew Burgess
2021-11-05 12:23 ` Tom de Vries
2021-11-05 12:55 ` Pedro Alves
2021-11-05 13:15 ` Tom de Vries
2021-11-05 13:20 ` Pedro Alves [this message]
2021-11-05 13:35 ` Tom de Vries
2021-11-05 13:52 ` Andrew Burgess
2021-12-06 15:27 ` Tom de Vries
2021-11-05 13:54 ` Pedro Alves
2021-12-06 15:25 ` Tom de Vries
2021-11-05 12:24 ` Pedro Alves
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=a687a8a2-3f53-739c-a022-bc2029bb1d04@palves.net \
--to=pedro@palves.net \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).