From: Joel Sherrill <joel@rtems.org>
To: Newlib <newlib@sourceware.org>
Subject: Fwd: All mips BSPs cannot link psxfenv01
Date: Sat, 15 Jan 2022 15:50:09 -0600 [thread overview]
Message-ID: <CAF9ehCWTccf6w5PRyBAcV+onZBY8pnv86G-VMzbiA=81kPVHEg@mail.gmail.com> (raw)
In-Reply-To: <3c8f49af-2e7c-73e4-6d14-c8dff5a78e04@embedded-brains.de>
I'm forwarding a discussion between Sebastian Huber and myself. Looks like
the mips fenv.h support was broken recently.
Any ideas?
---------- Forwarded message ---------
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
Date: Sat, Jan 15, 2022, 1:01 PM
Subject: Re: All mips BSPs cannot link psxfenv01
To: <joel@rtems.org>
Cc: RTEMS <devel@rtems.org>
On 14/01/2022 17:51, Joel Sherrill wrote:
>> Is this due to the recent Newlib build system changes?
> I guess so although I don't see anything obvious when I
> looked at the machine/configure.ac in both versions.
>
> I confirmed jmr3904 could build all tests with this gcc/newlib:
>
> $ ~/rtems-work/tools/6/bin/mips-rtems6-gcc --version
> mips-rtems6-gcc (GCC) 10.3.1 20211214 (RTEMS 6, RSB
> bb9e049b103f3a47019a6cfad18e2b59c9e9ea97, Newlib eb03ac1)
>
> That should have been the immediately previous version.
It is probably this change:
commit 8fa73a9f8414a4926365324c2fe32a237c2eb91d
Author: Jeff Johnston <jjohnstn@redhat.com>
Date: Mon Nov 29 17:33:52 2021 -0500
Modifying patch from: marian.buschsieweke@ovgu.de
The code accessing the floating point control/status register, namely
#define __cfc1(__fcsr) __asm __volatile("cfc1 %0, $31" :
"=r" (__fcsr)
does not compile with mips16. This changed the makefile to pass
-mno-mips16 to avoid the following
compiler error:
mips-mti-elf fails with "Error: unrecognized opcode `cfc1
$3,$31'"
I have no time to dig into the Newlib build system.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next parent reply other threads:[~2022-01-15 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c21d4a93-8643-2115-dfc0-0b278e15353c@embedded-brains.de>
[not found] ` <CAF9ehCV5eiSp7oOQiNKW1mFUmJE82D=RHuUSq6KFvhTKVt_h-g@mail.gmail.com>
[not found] ` <3c8f49af-2e7c-73e4-6d14-c8dff5a78e04@embedded-brains.de>
2022-01-15 21:50 ` Joel Sherrill [this message]
2022-02-07 6:43 ` Mike Frysinger
2022-02-07 14:29 ` Sebastian Huber
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='CAF9ehCWTccf6w5PRyBAcV+onZBY8pnv86G-VMzbiA=81kPVHEg@mail.gmail.com' \
--to=joel@rtems.org \
--cc=newlib@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).