mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ruggero rossi <rugrossi@googlemail.com>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] PTXDIST 2025.09.0: build failure of openssl-3.5.2 when gcc option -fzero-call-used-regs is not supported
Date: Wed, 17 Sep 2025 10:30:04 +0200	[thread overview]
Message-ID: <de26260c-079d-41c1-8a13-15deb79e53a7@t2data.com> (raw)
In-Reply-To: <20250917083239.145112e9@RR-Laptop>

Hi.

Which version of gcc are we talking about?
GCC 11 should support this, but I don't know over which archs.
It is there as a security enhancement. I would say something like less gadgets for ROP style attacks?
And while it does slow down execution, for something like OpenSSL, it usually is worth it imho.
I don't see a suitable toolchain option or hardening flag in ptxdist that currently fits this cleanly.
Not sure if something like this fits for a its own global pass either.
Maybe someone else has another opinion.

So my immediate suggestion would be to keep this local at your end for now.

Regards,
Christian

On 9/17/25 8:32 AM, ruggero rossi via ptxdist wrote:
> Hello everybody,
> 
> On my system, the gcc toolchain does not support the
> -fzero-call-used-regs option.
> 
> With PTXDIST 2025.09.0 this causes the build of OpenSSL 3.5.2 to fail.
> 
> An ad-hoc patch is trivial:
> I removed the -fzero-call-used-regs=used-gpr flag from
> openssl-3.5.2/Configurations/20-debian.conf (see attached patch).
> 
> My question is: would it be possible to integrate a more general solution
> into PTXDIST, so that the build works regardless of whether the toolchain
> supports this GCC option?
> 
> Best regards,
> 
> Ruggero Rossi
> 
> 
> 
> 
> 
> 
> 
> 
> 




  reply	other threads:[~2025-09-17  8:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  6:32 ruggero rossi via ptxdist
2025-09-17  8:30 ` Christian Melki [this message]
2025-09-17  9:00   ` ruggero rossi via ptxdist
2025-09-17  9:18     ` Christian Melki

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=de26260c-079d-41c1-8a13-15deb79e53a7@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=ptxdist@pengutronix.de \
    --cc=rugrossi@googlemail.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