Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/ramspeed: disable package if affected from gcc bug 43744
Date: Tue, 22 Aug 2023 22:09:39 +0200	[thread overview]
Message-ID: <20230822220939.1b53eca1@windsurf> (raw)
In-Reply-To: <20230813172524.354647-1-giulio.benetti@benettiengineering.com>

On Sun, 13 Aug 2023 19:25:24 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:

> This package is affected by gcc bug 43744 and I have not found a work
> around for it(i.e. the common -O0 we use or other), so let's disable it if
> gcc has such bug.
> 
> Fixes:
> http://autobuild.buildroot.net/results/ab289769c5fea435934ed260d38e0a4fdd2ba72d
> 
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
>  package/ramspeed/Config.in | 4 ++++
>  1 file changed, 4 insertions(+)

Applied to master, thanks. FYI, gcc bug 43744 is marked as RESOLVED
FIXED in the gcc bug tracker
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43744), so if you don't
reopen it, nobody is ever going to look into it :-/

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-08-22 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 17:25 [Buildroot] [PATCH] package/ramspeed: disable package if affected from gcc bug 43744 Giulio Benetti
2023-08-22 20:09 ` Thomas Petazzoni via buildroot [this message]
2023-08-22 20:47   ` Giulio Benetti
2023-09-13 15:55 ` 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=20230822220939.1b53eca1@windsurf \
    --to=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox