All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegorslists@googlemail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] poco: disable fpenvironment for MIPS without FPU
Date: Wed, 10 Oct 2018 09:05:11 +0200	[thread overview]
Message-ID: <CAGm1_ku-fnPuMW2NgL7DEiTa-=u2VnR8wyc41wPMhQJkRbEWhg@mail.gmail.com> (raw)
In-Reply-To: <CAGm1_kuA7Pp7gKP+1O_K0enyAf=OTFdcK-rhvTOrJYqiUMeWFQ@mail.gmail.com>

On Wed, Oct 10, 2018 at 9:02 AM Yegor Yefremov
<yegorslists@googlemail.com> wrote:
>
> On Wed, Oct 10, 2018 at 8:45 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
> >
> > Hello,
> >
> > On Tue, 9 Oct 2018 22:13:10 +0200, Arnout Vandecappelle wrote:
> >
> > >  The commit message is still very vague. I think I understand it though,
> > > something like:
> >
> > Yes, I agree the commit log was still too vague.
> >
> > > > +# MIPS without FPU
> > > > +ifeq ($(BR2_mips)$(BR2_mipsel)$(BR2_mips64)$(BR2_mips64el):$(BR2_MIPS_SOFT_FLOAT),y:y)
> > >
> > >  BR2_MIPS_SOFT_FLOAT is only defined on MIPS, so it is sufficient to do
> > >
> > > ifeq ($(BR2_MIPS_SOFT_FLOAT),y)
> > >
> > >  However, since this is about a glibc bug, shouldn't it check for a glibc
> > > toolchain as well?
> >
> > Isn't the glibc bug that it allowed to use fpenv in situations where it
> > shouldn't have allowed it ? If that's the case, perhaps the other
> > libcs didn't had this bug, and fpenv really shouldn't be used with MIPS
> > soft-float, regardless of the C library in use ?
>
> I've made a compile test with musl and it fails too. So I'll just
> disable fpenv if BR2_MIPS_SOFT_FLOAT is selected. So ne need to
> mention glibc.
>
> Strange, that it didn't show up in the build tests ...

For now we disable fpenv for two archs:

# architectures missing some FE_* in their fenv.h
ifeq ($(BR2_sh4a)$(BR2_nios2),y)
POCO_CONF_OPTS += --no-fpenvironment
endif

Should I just add $(BR2_MIPS_SOFT_FLOAT) to this statement even
without changing the comment?

Yegor

  reply	other threads:[~2018-10-10  7:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 13:21 [Buildroot] [PATCH v2] poco: disable fpenvironment for MIPS without FPU yegorslists at googlemail.com
2018-10-09 20:13 ` Arnout Vandecappelle
2018-10-10  6:45   ` Thomas Petazzoni
2018-10-10  7:02     ` Yegor Yefremov
2018-10-10  7:05       ` Yegor Yefremov [this message]
2018-10-10  7:12       ` Thomas Petazzoni
2018-10-10  7:14         ` Yegor Yefremov
2018-10-10  7:45           ` Arnout Vandecappelle
2018-10-10  8:23             ` Yegor Yefremov

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='CAGm1_ku-fnPuMW2NgL7DEiTa-=u2VnR8wyc41wPMhQJkRbEWhg@mail.gmail.com' \
    --to=yegorslists@googlemail.com \
    --cc=buildroot@busybox.net \
    /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.