Hi Matthias,
Matthias Klose, on 2023-08-24:
> please can you identify the object file which is wrongly built?
> build two versions, one with -O1, the other with -O2, then combine the
> object files from the two builds to identify a specific file?
Thanks for the procedure, I isolated that ParsInse
Étienne Mollier, on 2023-08-26:
> After suspecting hardening, it turned out
> that the following, when combined with build of ParsInsert.o
> with -O2 optimization, is causing the test failure:
>
> -specs=/usr/share/dpkg/no-pie-compile.specs
Rerunning these tests in a p
Hi Étienne,
Am Sun, Aug 27, 2023 at 11:26:32PM +0200 schrieb Étienne Mollier:
>
> Rerunning these tests in a properly isolate chroot show me that
> the hardening is also contributing to the improper results.
> Hardening must be disabled and PIE must be enforced to ensure
> the program runs approp
Hi Andreas,
Andreas Tille, on 2023-08-28:
> Am Sun, Aug 27, 2023 at 11:26:32PM +0200 schrieb Étienne Mollier:
> >
> > -O1 -O2 -O3
> > -fPIE + no hardening OK OKOK
> > -fno-PIE + no hardening OK FAIL FAIL
> > -fPIE + hardening OK
Hi Étienne,
Am Mon, Aug 28, 2023 at 10:09:42PM +0200 schrieb Étienne Mollier:
>
> The change even fixed LTO builds. :)
Nice.
> On the other hand, well, the hardening is gone. :(
>
> The package looks to range on the performance critical side of
> the spectrum, so this is probably an acceptab
5 matches
Mail list logo
