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++/109654] unnecessary "cannot bind packed field to reference" error when referenced type has aligned(1) attribute
Date: Thu, 27 Apr 2023 20:14:56 +0000	[thread overview]
Message-ID: <bug-109654-4-cvk39b0Gu0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109654-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109654

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=36566
         Resolution|---                         |INVALID

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This won't work for templates or function overloading since GCC does NOT mangle
the alignment.

This is why it was started to be rejected in the first place.

That is:
```
typedef __attribute__((aligned(1))) int packed_int;

template <class T> T load(T &a);

int load1(int *a)
{
  return load<packed_int>(*a);
}
int load2(int *a)
{
  return load<int>(*a);
}
```

Will both still call load<int> in both cases.

  reply	other threads:[~2023-04-27 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27 20:03 [Bug c++/109654] New: " richard-gccbugzilla at metafoo dot co.uk
2023-04-27 20:14 ` pinskia at gcc dot gnu.org [this message]
2023-04-28 21:09 ` [Bug c++/109654] " richard-gccbugzilla at metafoo dot co.uk
2023-05-12 20:49 ` pinskia at gcc dot gnu.org

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-109654-4-cvk39b0Gu0@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: 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).