From: Michael Meissner <meissner@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Michael Meissner <meissner@linux.ibm.com>,
gcc-patches@gcc.gnu.org, "Kewen.Lin" <linkw@linux.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
Peter Bergner <bergner@linux.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH 2/2] Rework 128-bit complex multiply and divide.
Date: Thu, 9 Mar 2023 18:23:31 -0500 [thread overview]
Message-ID: <ZApqcwGOKnyBlIXJ@toto.the-meissners.org> (raw)
In-Reply-To: <20230309221621.GV25951@gate.crashing.org>
On Thu, Mar 09, 2023 at 04:16:21PM -0600, Segher Boessenkool wrote:
> On Thu, Mar 09, 2023 at 11:11:34AM -0500, Michael Meissner wrote:
> > On Fri, Mar 03, 2023 at 03:35:44PM -0600, Segher Boessenkool wrote:
> > > > +/* { dg-final { scan-assembler "bl __divtc3" } } */
> > >
> > > This name depends on what object format and ABI is in use (some have an
> > > extra leading underscore, or a dot, or whatever).
> >
> > Yes it is needed if GCC is configured against an older GLIBC before the full
> > IEEE 128-bit support was added. For example, on my big endian test system, you
> > get warnings if you switch the floating point format. I would imagine it would
> > also fail on little endian system with older libraries.
>
> The regexp is not good enough, that is all. Maybe
> {bl .?__divtc3}
> or similar? We have many examples in the tests already.
I forgot the mention the regexp. I think just doing:
/* { dg-final { scan-assembler "__multc3" } } */
is sufficient.
--
Michael Meissner, IBM
PO Box 98, Ayer, Massachusetts, USA, 01432
email: meissner@linux.ibm.com
next prev parent reply other threads:[~2023-03-09 23:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 5:43 [PATCH 0/2] Repost of patches for solving the build on Fedora 36 problem Michael Meissner
2023-02-03 5:49 ` [PATCH 1/2] PR target/107299: Fix build issue when long double is IEEE 128-bit Michael Meissner
2023-02-22 10:37 ` Kewen.Lin
2023-02-22 18:11 ` Michael Meissner
2023-03-02 22:45 ` Ping: " Michael Meissner
2023-03-03 20:56 ` Segher Boessenkool
2023-02-03 5:53 ` [PATCH 2/2] Rework 128-bit complex multiply and divide Michael Meissner
2023-02-22 10:13 ` Kewen.Lin
2023-02-22 18:01 ` Michael Meissner
2023-03-02 22:46 ` Ping: " Michael Meissner
2023-03-03 21:35 ` Segher Boessenkool
2023-03-09 16:11 ` Michael Meissner
2023-03-09 22:16 ` Segher Boessenkool
2023-03-09 23:23 ` Michael Meissner [this message]
2023-03-09 16:42 ` Michael Meissner
2023-02-03 7:42 ` [PATCH 0/2] Repost of patches for solving the build on Fedora 36 problem Richard Biener
2023-02-06 18:28 ` Peter Bergner
2023-02-07 14:22 ` Richard Biener
2023-02-07 14:31 ` 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=ZApqcwGOKnyBlIXJ@toto.the-meissners.org \
--to=meissner@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linkw@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.ibm.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).