public inbox for
 help / color / mirror / Atom feed
From: Florian Weimer <>
To: James Hanley <>
Subject: Re: in6_addr struct union with uint64_t
Date: Mon, 29 Jan 2024 20:08:23 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (James Hanley's message of "Mon, 29 Jan 2024 13:02:11 -0500")

* James Hanley:

> I believe I understand your point - is the concern that the alignment
> issue would be manifested with an already compiled legacy application
> utilizing this newly built library and would require the in6_addr to
> be 16-byte aligned or hit a runtime exception if the address passed in
> isn't aligned - correct?

It's not so much the run-time exception/trap, but that struct offsets
may change as a result of the increased alignment.

If the compiler supports decreasing alignment, we could add the
additional arrays, but I'm not sure if that's worth it.


      reply	other threads:[~2024-01-29 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 14:57 James Hanley
2024-01-26 19:38 ` Florian Weimer
2024-01-29 18:02   ` James Hanley
2024-01-29 19:08     ` Florian Weimer [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).