From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH 1/2] package/fwts: Fix build with BR2_OPTIMIZE_0
Date: Sun, 9 Jul 2023 18:46:57 +0200 [thread overview]
Message-ID: <20230709184657.2658124d@windsurf> (raw)
In-Reply-To: <pan$c55d7$1b51cf8c$e75099b8$e4a39eb@ID-313208.user.individual.net>
Hello,
On Sun, 09 Jul 2023 18:42:31 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> yes, back in 2017: https://bugs.launchpad.net/fwts/+bug/1687049
>
> That bug report was solved by using -O2.
>
> Investigating further I found https://gcc.gnu.org/bugzilla/show_bug.cgi?
> id=102502#c4 which, to the best of my limited C knowledge, indicates that
> some assert code will not work with -O0 by design. At this point I
> stopped my research and disabled -O0 ;)
Alright, thanks for the additional details!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-09 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 9:50 [Buildroot] [PATCH 1/2] package/fwts: Fix build with BR2_OPTIMIZE_0 Bernd Kuhls
2023-07-09 9:50 ` [Buildroot] [PATCH 2/2] package/fwts: bump version to 23.07.00 Bernd Kuhls
2023-07-09 16:29 ` Thomas Petazzoni via buildroot
2023-07-09 16:29 ` [Buildroot] [PATCH 1/2] package/fwts: Fix build with BR2_OPTIMIZE_0 Thomas Petazzoni via buildroot
[not found] ` <20230709182938.00cef6ca__21548.8254021452$1688920206$gmane$org@windsurf>
2023-07-09 16:42 ` Bernd Kuhls
2023-07-09 16:46 ` Thomas Petazzoni via buildroot [this message]
2023-07-17 13:02 ` Peter Korsgaard
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=20230709184657.2658124d@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.org \
--cc=thomas.petazzoni@bootlin.com \
/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