From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 735353858C74; Thu, 12 Jan 2023 18:38:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 735353858C74
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1673548722;
	bh=k6ikLd6TeV1yusGMNSh7/9vBspDNwXyoPdbrUQQ1qLw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=CJbD+IIsp+kfFh0EDv8jvAcxM5SNtrvu4rgWEs92cOyXAyxjc30FzQX5zk625nvRN
	 Qqz2pC47AXUkBJub7j1yaPjvBb2Romnx/gFJaM/aOjZV5Fb433j4gOzxeJso0VoZuF
	 t45zoVffiCH9N2NEhZsRi6/Gjd0xerBgK8DVo+ec=
From: "m.novosyolov at rosalinux dot ru" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29979] Some -Wmaybe-uninitialized are needed on x86_32
 without -Os
Date: Thu, 12 Jan 2023 18:38:42 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: build
X-Bugzilla-Version: 2.36
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m.novosyolov at rosalinux dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29979-131-QNWSkJVWP1@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29979-131@http.sourceware.org/bugzilla/>
References: <bug-29979-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <glibc-bugs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D29979

--- Comment #2 from Mikhail Novosyolov <m.novosyolov at rosalinux dot ru> -=
--
(In reply to Adhemerval Zanella from comment #1)
> Right, which gcc version did you use it? I am checking with GCC 11 and I
> have not see any issue so far.

It is gcc 11:

$ gcc --version
gcc (GCC) 11.2.0 20210728 (ROSA)

I have provided full gcc cmdline with flags above, do not have any ideas el=
se
where the difference can be...

If it will help, here is a chroot in which this problem can be reproduced:

https://mirror.rosalinux.ru/rosa/rosa2021.1/iso/ROSA.FRESH.12/rootfs/rootfs=
-std-rosa2021.1_x86_64_2022-11-02.tar.xz

Or an installable livecd:
https://mirror.rosalinux.ru/rosa/rosa2021.1/iso/ROSA.FRESH.12/server/

To reproduce the problem, run:

sudo mkdir chroot
cd chroot
sudo tar -xf /path/to/rootfs-std-rosa2021.1_x86_64_2022-11-02.tar.xz
sudo systemd-nspawn -D . (or sudo chroot .)
# if running in VM, not chroot/container, start from here
dnf install basesystem-build /usr/bin/mbd git-core abf
git clone https://abf.io/import/glibc.git -b rosa2023.1
cd glibc
mbd glibc.spec
dnf install *.rpm (install build dependencies of glibc)

Comment out the patch described above:
-Patch10:       glibc-fix-ix86-build.patch
+#Patch10:      glibc-fix-ix86-build.patch

Run the build:
abf rpmbuild (just press enter when it asks questions about config)

gcc sources are here:
https://abf.io/import/gcc/tree/rosa2021.1

glibc with that problem:
https://abf.io/import/glibc/tree/rosa2023.1

--=20
You are receiving this mail because:
You are on the CC list for the bug.=