All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Andy Polyakov <appro@cryptogams.org>,
	Danny Tsen <dtsen@linux.ibm.com>,
	linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
	dtsen@us.ibm.com, nayna@linux.ibm.com,
	linux-kernel@vger.kernel.org, ltcgcw@linux.vnet.ibm.com,
	leitao@debian.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] crypto: X25519 low-level primitives for ppc64le.
Date: Thu, 16 May 2024 14:48:12 -0500	[thread overview]
Message-ID: <20240516194812.GN19790@gate.crashing.org> (raw)
In-Reply-To: <875xvevu3h.fsf@mail.lhotse>

Hi!

On Thu, May 16, 2024 at 10:06:58PM +1000, Michael Ellerman wrote:
> Andy Polyakov <appro@cryptogams.org> writes:
> >>> +.abiversion	2
> >>
> >> I'd prefer that was left to the compiler flags.
> >
> > Problem is that it's the compiler that is responsible for providing this
> > directive in the intermediate .s prior invoking the assembler. And there
> > is no assembler flag to pass through -Wa.
> 
> Hmm, right. But none of our existing .S files include .abiversion
> directives.
> 
> We build .S files with gcc, passing -mabi=elfv2, but it seems to have no
> effect.

Yup.  You coulds include some header file, maybe?  Since you run the
assembler code through the C preprocessor anyway, for some weird reason :-)

> But the actual code follows ELFv2, because we wrote it that way, and I
> guess the linker doesn't look at the actual ABI version of the .o ?

It isn't a version.  It is an actual different ABI.

GNU LD allows linking together whatever, yes.

> Is .abiversion documented anywhere? I can't see it in the manual.

Yeah me neither.  https://sourceware.org/bugzilla/enter_bug.cgi ?
A commandline flag (to GAS) would seem best?


Segher

WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: herbert@gondor.apana.org.au, dtsen@us.ibm.com,
	nayna@linux.ibm.com, linux-kernel@vger.kernel.org,
	Danny Tsen <dtsen@linux.ibm.com>,
	Andy Polyakov <appro@cryptogams.org>,
	linux-crypto@vger.kernel.org, ltcgcw@linux.vnet.ibm.com,
	leitao@debian.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] crypto: X25519 low-level primitives for ppc64le.
Date: Thu, 16 May 2024 14:48:12 -0500	[thread overview]
Message-ID: <20240516194812.GN19790@gate.crashing.org> (raw)
In-Reply-To: <875xvevu3h.fsf@mail.lhotse>

Hi!

On Thu, May 16, 2024 at 10:06:58PM +1000, Michael Ellerman wrote:
> Andy Polyakov <appro@cryptogams.org> writes:
> >>> +.abiversion	2
> >>
> >> I'd prefer that was left to the compiler flags.
> >
> > Problem is that it's the compiler that is responsible for providing this
> > directive in the intermediate .s prior invoking the assembler. And there
> > is no assembler flag to pass through -Wa.
> 
> Hmm, right. But none of our existing .S files include .abiversion
> directives.
> 
> We build .S files with gcc, passing -mabi=elfv2, but it seems to have no
> effect.

Yup.  You coulds include some header file, maybe?  Since you run the
assembler code through the C preprocessor anyway, for some weird reason :-)

> But the actual code follows ELFv2, because we wrote it that way, and I
> guess the linker doesn't look at the actual ABI version of the .o ?

It isn't a version.  It is an actual different ABI.

GNU LD allows linking together whatever, yes.

> Is .abiversion documented anywhere? I can't see it in the manual.

Yeah me neither.  https://sourceware.org/bugzilla/enter_bug.cgi ?
A commandline flag (to GAS) would seem best?


Segher

  parent reply	other threads:[~2024-05-16 19:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 17:38 [PATCH 0/3] crypto: X25519 supports for ppc64le Danny Tsen
2024-05-14 17:38 ` Danny Tsen
2024-05-14 17:38 ` [PATCH 1/3] crypto: X25519 low-level primitives " Danny Tsen
2024-05-14 17:38   ` Danny Tsen
2024-05-15  8:11   ` Andy Polyakov
2024-05-15  8:11     ` Andy Polyakov
2024-05-15 12:59     ` Danny Tsen
2024-05-15 12:59       ` Danny Tsen
2024-05-15  9:06   ` Andy Polyakov
2024-05-15  9:06     ` Andy Polyakov
2024-05-15 13:04     ` Danny Tsen
2024-05-15 13:04       ` Danny Tsen
2024-05-16  4:53   ` Michael Ellerman
2024-05-16  4:53     ` Michael Ellerman
2024-05-16  8:38     ` Andy Polyakov
2024-05-16  8:38       ` Andy Polyakov
2024-05-16 11:39       ` Danny Tsen
2024-05-16 11:39         ` Danny Tsen
2024-05-16 12:06       ` Michael Ellerman
2024-05-16 12:06         ` Michael Ellerman
2024-05-16 13:42         ` Andy Polyakov
2024-05-16 13:42           ` Andy Polyakov
2024-05-16 19:48         ` Segher Boessenkool [this message]
2024-05-16 19:48           ` Segher Boessenkool
2024-05-16 11:38     ` Danny Tsen
2024-05-16 11:38       ` Danny Tsen
2024-05-14 17:38 ` [PATCH 2/3] crypto: X25519 core functions " Danny Tsen
2024-05-14 17:38   ` Danny Tsen
2024-05-15  8:29   ` Andy Polyakov
2024-05-15  8:29     ` Andy Polyakov
2024-05-15 13:06     ` Danny Tsen
2024-05-15 13:06       ` Danny Tsen
2024-05-15 13:33     ` Andy Polyakov
2024-05-15 13:33       ` Andy Polyakov
2024-05-15 13:58       ` Danny Tsen
2024-05-15 13:58         ` Danny Tsen
2024-05-15 14:20         ` Andy Polyakov
2024-05-15 14:20           ` Andy Polyakov
2024-05-16 19:28     ` Segher Boessenkool
2024-05-16 19:28       ` Segher Boessenkool
2024-05-14 17:38 ` [PATCH 3/3] crypto: Update Kconfig and Makefile for ppc64le x25519 Danny Tsen
2024-05-14 17:38   ` Danny Tsen

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=20240516194812.GN19790@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=appro@cryptogams.org \
    --cc=dtsen@linux.ibm.com \
    --cc=dtsen@us.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=leitao@debian.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ltcgcw@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=nayna@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.