From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Landley <rob@landley.net>
Cc: Finn Thain <fthain@telegraphics.com.au>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
"Linux/m68k" <linux-m68k@vger.kernel.org>,
Laurent Vivier <Laurent@vivier.eu>
Subject: Re: GCC?, was Re: Running m68k on qemu with external initramfs?
Date: Mon, 13 Apr 2020 11:42:04 +0200 [thread overview]
Message-ID: <CAMuHMdXyhB52yLZ59njZ6fTZB8B1cZNWLFHcGaCxZ2TuKt7_0g@mail.gmail.com> (raw)
In-Reply-To: <29e2cf8a-35fa-b24a-bce2-84e05e54d4c5@landley.net>
Hi Rob,
On Mon, Apr 13, 2020 at 11:37 AM Rob Landley <rob@landley.net> wrote:
> On 4/13/20 2:07 AM, Rob Landley wrote:
> >> It would be great to have a minimal reproducer from toysh. Getting that
> >> from the python build looks hard, even with creduce.
> >> https://embed.cs.utah.edu/creduce/
> >
> > Oh it's not hard, it's just tedious.
>
> Did you know that if you disable optimizations you can get _more_ warnings?
>
> _disabling_ the gcse optimization triggered one of those "may be used
> uninitialized but is a false positive 99% of the time" which in this case,
> turned out to have a path that could trigger in a function I added last week,
> which which was called in an else case 5 lines down. (Yes, when it DIDN'T
> segfault, it gave me the warning.)
It's indeed a pity. I looked into each and every one of them when I could
still compile the kernel with gcc 4.1, to find the few cases that were real
bugs...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2020-04-13 9:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 0:50 Running m68k on qemu with external initramfs? Rob Landley
2020-04-11 6:12 ` Finn Thain
2020-04-12 3:36 ` Rob Landley
2020-04-12 5:29 ` Finn Thain
2020-04-12 12:34 ` Rob Landley
2020-04-12 8:27 ` John Paul Adrian Glaubitz
2020-04-12 8:31 ` Laurent Vivier
2020-04-12 21:48 ` Rob Landley
2020-04-12 23:17 ` Finn Thain
2020-04-11 12:12 ` John Paul Adrian Glaubitz
2020-04-12 12:48 ` Rob Landley
2020-04-12 13:02 ` John Paul Adrian Glaubitz
2020-04-12 21:56 ` Rob Landley
2020-04-12 23:30 ` GCC?, was " Finn Thain
2020-04-13 0:28 ` Rob Landley
2020-04-13 5:17 ` Finn Thain
2020-04-13 7:07 ` Rob Landley
2020-04-13 7:41 ` John Paul Adrian Glaubitz
2020-04-13 8:27 ` Rob Landley
2020-04-13 9:42 ` Geert Uytterhoeven [this message]
2020-04-13 23:02 ` Finn Thain
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=CAMuHMdXyhB52yLZ59njZ6fTZB8B1cZNWLFHcGaCxZ2TuKt7_0g@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=Laurent@vivier.eu \
--cc=fthain@telegraphics.com.au \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=rob@landley.net \
/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 NNTP newsgroup(s).