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++/106873] unsigned short skips byte when used for memory mapping depending on position in structure
Date: Wed, 07 Sep 2022 16:28:02 +0000	[thread overview]
Message-ID: <bug-106873-4-b735SJbVov@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106873-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> Which I think is what you are missing is that the ABI is layed out this way.

The reason why it is layout this way is for alignment reasons. In many ABIs,
the alignment of short is 2 bytes; the natural alignment.

  parent reply	other threads:[~2022-09-07 16:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 16:18 [Bug libstdc++/106873] New: " info at kemalakcam dot com
2022-09-07 16:26 ` [Bug c++/106873] " pinskia at gcc dot gnu.org
2022-09-07 16:28 ` pinskia at gcc dot gnu.org [this message]
2022-09-07 16:35 ` info at kemalakcam dot com
2022-09-07 16:45 ` pinskia at gcc dot gnu.org
2022-09-07 17:01 ` redi at gcc dot gnu.org
2022-09-12  3:16 ` info at kemalakcam dot com

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-106873-4-b735SJbVov@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).