Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [pushed] [gdb/build, clang] Fix ignored aligned attribute
Date: Fri, 12 Jun 2026 14:26:03 +0100	[thread overview]
Message-ID: <27af1313-53fc-4de7-a707-4f24b0e51441@palves.net> (raw)
In-Reply-To: <20260612104134.4147876-1-tdevries@suse.de>

On 2026-06-12 11:41, Tom de Vries wrote:
> PR build/34279 reports a build failure with clang.
> 
> This is a regression since commit 6c85ef111b0 ("[gdb] Use using instead of
> typedef"), which did:
> ...
> -typedef long __attribute__ ((__aligned__ (4))) compat_x32_clock_t;
> +using compat_x32_clock_t = long __attribute__ ((__aligned__ (4)));
> ...
> 
> The problem is that clang ignores the attribute.

FYI, this form:

  using B [[gnu::aligned (4)]] = long;

works the same with gcc and clang.


  parent reply	other threads:[~2026-06-12 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 10:41 Tom de Vries
2026-06-12 13:24 ` Tom Tromey
2026-06-16  7:26   ` Tom de Vries
2026-06-12 13:26 ` Pedro Alves [this message]
2026-06-16  6:27   ` Tom de Vries

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=27af1313-53fc-4de7-a707-4f24b0e51441@palves.net \
    --to=pedro@palves.net \
    --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