From: Georg-Johann Lay <gjl@gcc.gnu.org>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Denis Chertykov <chertykov@gmail.com>
Subject: [PING^1][patch,avr, 0/3] Support 64-bit (long) double.
Date: Sat, 28 Dec 2019 11:59:00 -0000 [thread overview]
Message-ID: <5E074255.2030500@gcc.gnu.org> (raw)
In-Reply-To: <268c2e7e-aca7-58fa-602c-6b9dafc133e7@gjlay.de>
Ping #1
> Now that the avr backend can support 64-bit floats by means of
> configure-options --with-double= and --with-long-double=, this patch
> series adds some routines to support it.
>
> It's an ad-hoc, avr-specific implementation in assembly and GNU-C which
> is added as a new subfolder in libgcc/config/avr/libf7.
>
> Patch 1/3 is the GCC changes: Documentation and new avr-specific
> configure options:
>
> --with-libf7 selects to which level double support from libf7 is added
> to libgcc.
>
> --with-double-comparison select what FLOAT_LIB_COMPARE_RETURNS_BOOL
> returns.
>
> I wrote the libf7 code from scratch and put it under GPL v3 + library
> exception, so it should be no problem to have it as part of libgcc.
>
> Patch 2/3 is the libgcc additions:
>
> --with-libf7 selects which makefile-snips from libf7 to use.
>
> Patch 3/3 is the actual libf7 implementation. A great deal of which is
> assembly, together with C + inline assembly for higher routines.
>
> Ok for trunk?
>
> Johann
>
next prev parent reply other threads:[~2019-12-28 11:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 16:43 [patch,avr, " Georg-Johann Lay
2019-12-16 16:46 ` [patch,avr, 1/3] Support 64-bit (long) double: The gcc part Georg-Johann Lay
2019-12-28 13:20 ` [PING^1][patch,avr, " Georg-Johann Lay
2020-01-06 13:08 ` [Ping^2][patch,avr, " Georg-Johann Lay
2020-01-06 16:25 ` [patch,avr, " Jeff Law
2020-01-06 17:10 ` Georg-Johann Lay
2020-01-06 17:16 ` Jeff Law
2020-12-15 7:40 ` AVR maintainership (was: [patch,avr, 1/3] Support 64-bit (long) double: The gcc part.) Gerald Pfeifer
2020-12-15 14:30 ` AVR maintainership (was: [patch, avr, " Segher Boessenkool
2020-12-15 20:42 ` AVR maintainership (was: [patch,avr, " Jeff Law
2020-12-18 16:53 ` AVR maintainership Georg-Johann Lay
2019-12-16 16:49 ` [patch,avr, 2/3] Support 64-bit (long) double: The libgcc changes Georg-Johann Lay
2019-12-28 12:00 ` [PING^1][patch,avr, " Georg-Johann Lay
2020-01-06 13:08 ` [Ping^2][patch,avr, " Georg-Johann Lay
2020-01-06 16:26 ` [patch,avr, " Jeff Law
2019-12-16 17:09 ` [patch,avr, 3/3] Support 64-bit (long) double: libf7 Georg-Johann Lay
2019-12-28 12:02 ` [PING^1][patch,avr, " Georg-Johann Lay
2020-01-06 13:09 ` [Ping^2][patch,avr, " Georg-Johann Lay
2020-01-06 16:26 ` [patch,avr, " Jeff Law
2019-12-28 11:59 ` [PING^1][patch,avr, 0/3] Support 64-bit (long) double Georg-Johann Lay
2019-12-28 11:59 ` Georg-Johann Lay [this message]
2020-01-06 13:08 ` [Ping^2][patch,avr, " Georg-Johann Lay
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=5E074255.2030500@gcc.gnu.org \
--to=gjl@gcc.gnu.org \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.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).