From: Peter Korsgaard <peter@korsgaard.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Maxim Kochetkov <fido_max@inbox.ru>,
Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/postgresql: work around gcc bug 43744
Date: Wed, 22 Feb 2023 17:22:54 +0100 [thread overview]
Message-ID: <87fsaxvfdt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20230202154239.325711-2-giulio.benetti@benettiengineering.com> (Giulio Benetti's message of "Thu, 2 Feb 2023 16:42:39 +0100")
>>>>> "Giulio" == Giulio Benetti <giulio.benetti@benettiengineering.com> writes:
> Package postgresql suffers from gcc bug 43744 other than 85180, so let's
> work around disabling compiler optimization for this gcc bug too.
> Fixes:
> http://autobuild.buildroot.net/results/cf272cdc5be2faf4070de3d235ec7a0f7190867a
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed to 2022.11.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-22 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 15:42 [Buildroot] [PATCH 1/2] toolchain/Config.in: extend gcc bug 43744 to every sh architecture Giulio Benetti
2023-02-02 15:42 ` [Buildroot] [PATCH 2/2] package/postgresql: work around gcc bug 43744 Giulio Benetti
2023-02-06 11:21 ` Thomas Petazzoni via buildroot
2023-02-06 13:26 ` Giulio Benetti
2023-02-22 16:22 ` Peter Korsgaard [this message]
2023-02-05 12:15 ` [Buildroot] [PATCH 1/2] toolchain/Config.in: extend gcc bug 43744 to every sh architecture Thomas Petazzoni via buildroot
2023-02-05 21:25 ` [Buildroot] [PATCH v2] " Giulio Benetti
2023-02-06 9:46 ` Thomas Petazzoni via buildroot
2023-02-22 15:48 ` 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=87fsaxvfdt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fido_max@inbox.ru \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.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.