DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>, dev@dpdk.org
Subject: Re: [PATCH] build: force gcc to initialize padding bits
Date: Fri, 24 Jan 2025 10:37:48 -0800	[thread overview]
Message-ID: <20250124103748.6b9b85fa@hermes.local> (raw)
In-Reply-To: <Z5NfjMe4BRwtPjUm@bricha3-mobl1.ger.corp.intel.com>

On Fri, 24 Jan 2025 09:38:20 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:

> >   
> 
> Does this flag give us additional guarantees of padding being
> zero-initialized that were there before? From my reading of the gcc doc[1],
> "..padding-bits=union" corresponds to the old behaviour, right?
> 
> This also means we will have different padding behaviour on clang and gcc,
> since clang (at least v18 on my board) doesn't support this flag. Do we see
> any issues with that?
> 
> /Bruce

I chose the setting based on some email with the Linux kernel hardening
project and their choice.

Clang decided to fix and just do the right thing.


https://github.com/llvm/llvm-project/commit/7a086e1b2dc05f54afae3591614feede727601fa

  reply	other threads:[~2025-01-24 18:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-23 17:20 Stephen Hemminger
2025-01-24  7:48 ` Morten Brørup
2025-01-24  9:38   ` Bruce Richardson
2025-01-24 18:37     ` Stephen Hemminger [this message]
2025-01-24 18:26 ` [PATCH v2] " Stephen Hemminger

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=20250124103748.6b9b85fa@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.com \
    /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 NNTP newsgroup(s).