From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/libpcap: fix m68k-cf compile issue
Date: Thu, 15 Aug 2024 09:19:28 +0200 [thread overview]
Message-ID: <20240815091928.4478068d@windsurf> (raw)
In-Reply-To: <Zr1DUNSWk+fNwdzx@waldemar-brodkorb.de>
On Thu, 15 Aug 2024 01:52:49 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> Compilation with -Os triggers this assembler problem.
> The problematic C code contains a long switch statement, so
> everything looks like GCC Bug 104028 is triggered.
>
> Fixes:
> - http://autobuild.buildroot.net/results/db5/db58215fb3c7f30b6c0f0764a84271010346edfb
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1->v2:
> - use GCC_BUG_XXXXXX instead of arch sepcific stuff, requested by
> Thomas Petazzoni
> ---
> package/libpcap/libpcap.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Applied to master, thanks.
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
next prev parent reply other threads:[~2024-08-15 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 23:52 [Buildroot] [PATCH] package/libpcap: fix m68k-cf compile issue Waldemar Brodkorb
2024-08-15 7:19 ` Thomas Petazzoni via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-14 13:09 Waldemar Brodkorb
2024-08-14 17:57 ` Thomas Petazzoni via buildroot
2024-08-14 18:00 ` Waldemar Brodkorb
2024-08-14 19:13 ` Thomas Petazzoni via buildroot
2024-09-16 9:26 ` 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=20240815091928.4478068d@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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