public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108342] std::complex: ignoring packed attribute because of unpacked non-POD field Date: Mon, 09 Jan 2023 16:37:40 +0000 [thread overview] Message-ID: <bug-108342-4-79hcaLv4dP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108342-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108342 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=13983, | |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=17519 --- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> --- r0-51814-ge0d1297c4320ae added the warning and started to ignore the packed (back in 2003).
next prev parent reply other threads:[~2023-01-09 16:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-09 12:57 [Bug c++/108342] New: " ruilvo at ua dot pt 2023-01-09 16:08 ` [Bug c++/108342] " pinskia at gcc dot gnu.org 2023-01-09 16:13 ` [Bug libstdc++/108342] " pinskia at gcc dot gnu.org 2023-01-09 16:14 ` ruilvo at ua dot pt 2023-01-09 16:16 ` ruilvo at ua dot pt 2023-01-09 16:17 ` redi at gcc dot gnu.org 2023-01-09 16:28 ` [Bug c++/108342] " pinskia at gcc dot gnu.org 2023-01-09 16:31 ` pinskia at gcc dot gnu.org 2023-01-09 16:37 ` pinskia at gcc dot gnu.org [this message] 2023-01-09 16:39 ` pinskia at gcc dot gnu.org 2023-01-09 21:23 ` ruilvo at ua dot pt 2023-01-09 21:34 ` jakub at gcc dot gnu.org 2023-01-09 21:40 ` ruilvo at ua dot pt
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-108342-4-79hcaLv4dP@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).