public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pedro at palves dot net" <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 14:48:14 +0000 [thread overview] Message-ID: <bug-29373-4717-lQ9aPbwb2J@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 #7 from Pedro Alves <pedro at palves dot net> --- Googling around, I found that Clang for Windows does not support the gcc_struct attribute. E.g., here: https://code.videolan.org/videolan/libdvdread/-/issues/19 with that in mind, I added back (or rather, reimplemented), the fallback implementation using byte arrays, and make _WIN32 + clang use it. To make sure it all behaves as intended, I wrote some units tests. I don't think I'll have to post this to the list today, so I pushed it to the users/palves/packed branch on sourceware. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-07-19 14:48 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 2022-07-19 11:49 ` pedro at palves dot net 2022-07-19 14:48 ` pedro at palves dot net [this message] 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-lQ9aPbwb2J@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: linkBe 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).