Hi! On Tue, 9 May 2023 at 11:00, Thomas Schwinge <tho...@codesourcery.com> wrote:
> Hi Christophe! > > On 2023-05-09T09:32:55+0200, Christophe Lyon <christophe.l...@linaro.org> > wrote: > > On Wed, 3 May 2023 at 13:47, Richard Biener via Gcc-patches < > gcc-patches@gcc.gnu.org> wrote: > >> On Wed, 3 May 2023, Thomas Schwinge wrote: > >> > "Let each 'lto_init' determine the default 'LTO_OPTIONS', and > 'torture-init' the 'LTO_TORTURE_OPTIONS'"? > > > > This is causing issues on arm/aarch64, including: > > > > ERROR: can't read "LTO_TORTURE_OPTIONS": no such variable > > in gcc.target/arm/acle/acle.exp: > > > > ERROR: torture-init: LTO_TORTURE_OPTIONS is not empty as expected > > in gcc.target/aarch64/sls-mitigation/sls-mitigation.exp, > > gcc.target/aarch64/sve/acle/aarch64-sve-acle-asm.exp, > > gcc.target/aarch64/sve2/acle/aarch64-sve2-acle-asm.exp, > > gcc.target/aarch64/torture/aarch64-torture.exp > > > > and maybe others > > > > Are other targets affected too? > > Sorry for that -- it means, the safe-guards I added are working as > expected. > > Please test whether all these issues are gone with the attached > "Testsuite: Add missing 'torture-init'/'torture-finish' around > 'LTO_TORTURE_OPTIONS' usage"? > > Your patch seemed reasonable, but it doesn't work :-( Well now I get: ERROR: torture-init: LTO_TORTURE_OPTIONS is not empty as expected because gcc-dg-runtest itself calls torture-init but I'm not sure where LTO_TORTURE_OPTIONS is set Christophe > Grüße > Thomas > > > ----------------- > Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, > 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: > Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; > Registergericht München, HRB 106955 >
