From: Waldemar Brodkorb <wbx@openadk.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] arch/or1k: fix uClibc issues with fenv enabled
Date: Sun, 30 Aug 2026 19:28:21 +0200 [thread overview]
Message-ID: <apRoNTQRjDuv0m-O@waldemar-brodkorb.de> (raw)
In-Reply-To: <apLFfy3hJ6NSAWkv@windsurf>
Hi Thomas,
Thomas Petazzoni wrote,
> Hello,
>
> On Sat, Aug 29, 2026 at 01:39:26PM +0200, Thomas Petazzoni wrote:
>
> > But more importantly, I don't see how your patch fixes the soft float
> > situation. My understanding is that soft-float is the default on
> > OR1K. Your patch doesn't change *anything* in soft-float
> > configuration, it only passes -mhard-float in hard float
> > configurations, and makes hard float the default.
> >
> > How can your patch fix anything with BR2_OR1K_SOFT_FLOAT enabled?
>
> Sorry for my mistake, but re-reading, I know understand:
> BR2_OR1K_SOFT_FLOAT selects BR2_SOFT_FLOAT, and based on that uClibc
> uses or doesn't use hard-float fenv stuff. That makes sense.
>
> Still the patch seems incorrect to me, and should modify gcc.mk and
> the toolchain external stuff instead.
As I stated in my other mail --with-float is not available for gcc
on or1k. How should I proceed? How does the toolchain-wrapper
recognizes the user wants a hard-float toolchain?
For the external toolchains I understand it, but not for the
internal BR toolchains.
best regards
Waldemar
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-08-30 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 22:15 [Buildroot] [PATCH] arch/or1k: fix uClibc issues with fenv enabled Waldemar Brodkorb
2026-08-29 11:39 ` Thomas Petazzoni via buildroot
2026-08-29 11:42 ` Thomas Petazzoni via buildroot
2026-08-30 17:28 ` Waldemar Brodkorb [this message]
2026-08-30 17:22 ` Waldemar Brodkorb
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=apRoNTQRjDuv0m-O@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--cc=buildroot@buildroot.org \
--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.