public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-29979-131-QNWSkJVWP1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29979-131@http.sourceware.org/bugzilla/>

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

--- 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 else
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

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

      parent reply	other threads:[~2023-01-12 18:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-09 20:19 [Bug build/29979] New: " m.novosyolov at rosalinux dot ru
2023-01-09 20:22 ` [Bug build/29979] " m.novosyolov at rosalinux dot ru
2023-01-12 13:31 ` adhemerval.zanella at linaro dot org
2023-01-12 18:38 ` m.novosyolov at rosalinux dot ru [this message]

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=bug-29979-131-QNWSkJVWP1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).