public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29373] Canadian Compilation Failed! gdbsupport/packed.h:41:40: error: static assertion failed for x86_64-w64-mingw32 host.
Date: Tue, 19 Jul 2022 04:21:47 +0000	[thread overview]
Message-ID: <bug-29373-4717-Yw8pIn9K2j@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29373-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29373

--- Comment #5 from cqwrteur <euloanty at live dot com> ---
(In reply to Pedro Alves from comment #4)
> I can reproduce this here, cross building with mingw on Fedora.
> 
> This is indeed an ABI issue -- mingw defaults to "-mms-bitfields", which
> affects how bitfields are laid out.  Luckily, there's an attribute to switch
> ABI on a per struct basis.  See:
> 
>   https://gcc.gnu.org/onlinedocs/gcc/x86-Variable-Attributes.html
> 
> This fixes the build for me:
> 
> diff --git c/gdbsupport/packed.h w/gdbsupport/packed.h
> index 3468cf44207..a3389afdfb7 100644
> --- c/gdbsupport/packed.h
> +++ w/gdbsupport/packed.h
> @@ -20,6 +20,12 @@
>  
>  #include "traits.h"
>  
> +#ifdef __MINGW32__
> +# define ATTRIBUTE_GCC_STRUCT  __attribute__((gcc_struct))
> +#else
> +# define ATTRIBUTE_GCC_STRUCT
> +#endif
> +
>  /* Each instantiation and full specialization of the packed template
>     defines a type that behaves like a given scalar type, but that has
>     byte alignment, and, may optionally have a smaller size than the
> @@ -58,7 +64,7 @@ struct packed
>  
>  private:
>    T m_val : (Bytes * HOST_CHAR_BIT) ATTRIBUTE_PACKED;
> -};
> +} ATTRIBUTE_GCC_STRUCT;
>  
>  /* Add some comparisons between std::atomic<packed<T>> and T.  We need
>     this because the regular comparisons would require two implicit

Also cygwin and other pe targets.

you probably need 


#if __has_cpp_attribute(__gnu__::__gcc_struct__)
#define ATTRIBUTE_GCC_STRUCT [[__gnu__::__gcc_struct__]]
#endif

something like that to detect the feature

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-07-19  4:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-16 20:52 [Bug build/29373] New: " euloanty at live dot com
2022-07-16 20:52 ` [Bug build/29373] " euloanty at live dot com
2022-07-16 20:53 ` euloanty at live dot com
2022-07-18 18:31 ` tromey at sourceware dot org
2022-07-18 18:33 ` tromey at sourceware dot org
2022-07-18 21:18 ` vries at gcc dot gnu.org
2022-07-18 23:34 ` pedro at palves dot net
2022-07-19  4:21 ` euloanty at live dot com [this message]
2022-07-19 11:49 ` pedro at palves dot net
2022-07-19 14:48 ` pedro at palves dot net
2022-07-19 14:48 ` pedro at palves dot net
2022-07-21 12:24 ` vries at gcc dot gnu.org
2022-07-21 13:45 ` pedro at palves dot net
2022-07-21 14:34 ` pedro at palves dot net
2022-07-21 14:53 ` vries at gcc dot gnu.org
2022-07-21 15:27 ` pedro at palves dot net
2022-07-25 15:12 ` cvs-commit at gcc dot gnu.org
2022-07-25 15:20 ` pedro at palves dot net

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=bug-29373-4717-Yw8pIn9K2j@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).