From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: Giulio Benetti <giulio.benetti@benettiengineering.com>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [External] - [PATCH] package/attr: fix build failure on Microblaze architecture
Date: Tue, 6 Feb 2024 17:25:40 +0100 [thread overview]
Message-ID: <20240206172540.2d1ed291@windsurf> (raw)
In-Reply-To: <PH1P110MB160351713AB054CEFD33B1439F46A@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>
Hello Vincent,
On Tue, 6 Feb 2024 16:05:31 +0000
Vincent Fazio <vfazio@xes-inc.com> wrote:
> Would it make sense to patch GCC for Microblaze to address these at
> the compiler level instead of constantly patching the packages?
>
> I tested https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101766#c6 back
> when we were solving this problem for xz and had no issues
> https://gcc.gnu.org/pipermail/gcc/2023-March/240834.html
It would definitely make sense of course. Have you been able to get the
necessary changes accepted in upstream GCC ?
Thanks!
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:[~2024-02-06 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 6:58 [Buildroot] [PATCH v2, 1/2] toolchain: add BR2_TOOLCHAIN_HAS_GCC_BUG_101766 Fabrice Fontaine
2024-01-16 6:58 ` [Buildroot] [PATCH v2, 2/2] package/attr: affected by gcc bug 101766 Fabrice Fontaine
2024-02-06 15:11 ` Thomas Petazzoni via buildroot
2024-02-06 15:20 ` Giulio Benetti
2024-02-06 15:54 ` [Buildroot] [PATCH] package/attr: fix build failure on Microblaze architecture Giulio Benetti
2024-02-06 16:05 ` [Buildroot] [External] - " Vincent Fazio
2024-02-06 16:15 ` Giulio Benetti
2024-02-06 16:25 ` Thomas Petazzoni via buildroot [this message]
2024-02-06 16:38 ` Vincent Fazio
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=20240206172540.2d1ed291@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.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