From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Giulio Benetti <giulio.benetti+tekvox@benettiengineering.com>,
James Autry <jautry@tekvox.com>, Jim Reinhart <jimr@tekvox.com>,
Matthew Maron <matthewm@tekvox.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/swupdate: workaround runtime update failure
Date: Wed, 29 Nov 2023 22:38:08 +0100 [thread overview]
Message-ID: <20231129223808.19195702@windsurf> (raw)
In-Reply-To: <1c744e50-01e2-4e78-94b1-62b6ebfd992d@benettiengineering.com>
Hello Giulio,
On Sat, 25 Nov 2023 01:24:45 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> > Is there a compiler bug? Or a bug in
> > the swupdate code base, such as some undefined behavior that causes an
> > incorrect behavior when built -Os, but not -O3 ?
>
> An undefined behavior showing up when built with -Os, but I'm currently
> trying to work it out and also to give a test case to SWUpdate
> Maintainer using qemu-arm.
>
> So I think it's better I get to the root cause, I fix it and later
> provide a local patch to fix the problem.
Sounds good, thanks for the effort.
> I've already set the patch as Rejected on Patchwork, sorry for the
> noise.
No worries at all!
Best regards,
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
prev parent reply other threads:[~2023-11-29 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 17:39 [Buildroot] [PATCH] package/swupdate: workaround runtime update failure Giulio Benetti
2023-11-24 21:59 ` Thomas Petazzoni via buildroot
2023-11-25 0:24 ` Giulio Benetti
2023-11-29 21:38 ` Thomas Petazzoni via buildroot [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=20231129223808.19195702@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti+tekvox@benettiengineering.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=jautry@tekvox.com \
--cc=jimr@tekvox.com \
--cc=matthewm@tekvox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.