From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 4C779385842C; Mon, 23 Aug 2021 15:21:37 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4C779385842C
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/102017] libgcc ieee754-df.S for arm does not support
 exceptions
Date: Mon, 23 Aug 2021 15:21:37 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 12.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-102017-4-FzASYwjm2A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102017-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Aug 2021 15:21:37 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102017

--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
There are a number of complications here:
- What's the code size overhead?  Even if the performance overhead is trivi=
al,
I suspect the additional code might be non-trivial on an m-profile device, =
so
is there a simple way to choose not to link such support in when not
needed/wanted?  Perhaps it could be done by using some weak function calls =
for
raising the exceptions and then only link the stub code in if there are cal=
ls
to fe*().
- How would it work in a hybrid -mfloat-abi=3Dsoft + -mfloat-abi=3Dsoftfp
environment?  See the point above again, especially if the float-env testing
routines can get inlined.=