From: Christophe Lyon <christophe.lyon@linaro.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Eric Botcazou <botcazou@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] Fix PR middle-end/98099
Date: Fri, 4 Dec 2020 10:22:01 +0100 [thread overview]
Message-ID: <CAKdteOZdf6bmyRFLrmyR1XHvcP5c-viZXERrTEUyXCN1CWYFsw@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc1uMGJN+5gVNWf7kz6dajGLWwOCwgsD6P6E_zfJt66B4g@mail.gmail.com>
On Thu, 3 Dec 2020 at 13:33, Richard Biener via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> On Thu, Dec 3, 2020 at 11:49 AM Eric Botcazou <botcazou@adacore.com> wrote:
> >
> > Hi,
> >
> > this replaces the ICE by a sorry message for the use of reverse scalar storage
> > order with a 128-bit decimal floating-point type on 32-bit platforms.
> >
> > Tested on x86-64/Linux, OK for the mainline?
>
> OK.
>
> Richard.
>
> >
> > 2020-12-03 Eric Botcazou <ebotcazou@adacore.com>
> >
> > * expmed.c (flip_storage_order): In the case of a non-integer mode,
> > sorry out if the integer mode to be used instead is not supported.
> >
> >
> > 2020-12-03 Eric Botcazou <ebotcazou@adacore.com>
> >
> > * gcc.dg/pr98099.c: New test.
> >
I think you need to add an effective-target check, because the new test
fails on aarch64/arm:
FAIL: gcc.dg/pr98099.c (test for excess errors)
Excess errors:
/gcc/testsuite/gcc.dg/pr98099.c:7:12: error: decimal floating-point
not supported for this target
/gcc/testsuite/gcc.dg/pr98099.c:9:1: error: decimal floating-point not
supported for this target
Christophe
> > --
> > Eric Botcazou
next prev parent reply other threads:[~2020-12-04 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 10:47 Eric Botcazou
2020-12-03 12:33 ` Richard Biener
2020-12-04 9:22 ` Christophe Lyon [this message]
2020-12-04 9:29 ` Eric Botcazou
2021-03-18 8:57 ` [committed] testsuite: Fix up pr98099.c testcase for big endian [PR98099] Jakub Jelinek
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=CAKdteOZdf6bmyRFLrmyR1XHvcP5c-viZXERrTEUyXCN1CWYFsw@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.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 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).