From: Georg-Johann Lay <avr@gjlay.de>
To: law@redhat.com
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch,avr, 1/3] Support 64-bit (long) double: The gcc part.
Date: Mon, 06 Jan 2020 17:10:00 -0000 [thread overview]
Message-ID: <5E136A67.5010301@gjlay.de> (raw)
In-Reply-To: <de16e5ae946975ad42f670ebf67caaaae7e714a6.camel@redhat.com>
Jeff Law schrieb:
> On Mon, 2019-12-16 at 17:43 +0100, Georg-Johann Lay wrote:
>> Am 16.12.19 um 17:40 schrieb Georg-Johann Lay:
>> 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.
>>
>> Johann
>>
>> gcc/
>> * config.gcc (tm_defines) [target=avr]: Support --with-libf7,
>> --with-double-comparison.
>> * doc/install.texi: Document them.
>> * config/avr/avr-c.c (avr_cpu_cpp_builtins)
>> <WITH_LIBF7_LIBGCC, WITH_LIBF7_MATH, WITH_LIBF7_MATH_SYMBOLS>
>> <WITH_DOUBLE_COMPARISON>: New built-in defines.
>> * doc/invoke.texi (AVR Built-in Macros): Document them.
>> * config/avr/avr-protos.h (avr_float_lib_compare_returns_bool): New.
>> * config/avr/avr.c (avr_float_lib_compare_returns_bool): New function.
>> * config/avr/avr.h (FLOAT_LIB_COMPARE_RETURNS_BOOL): New macro.
> I'd suggest "--with-libf77" rather than "--with-libf7".
>
> jeff
Why that second 7?
I called it "libf7" because the internal _f_loat representation has a
mantissa of 7 bytes. So libf56 would also be indicative.
Actually the name does not matter very much... It just needs to have
/some/ name. "f77" however puts it close to Fortran, but that code has
absolutely nothing to do with Fortran whatsoever.
Johann
p.s. You know anything about Denis Chertykov? He used to reply to avr
patches within hours, but my latest patches (after a long period where I
didn't propose any patches) where all approved by you; not a single mail
from Denis. So I am concerned if he's well. Maybe he left you or some
other global maintainer a note? He's still listed as maintainer though.
next prev parent reply other threads:[~2020-01-06 17:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 16:43 [patch,avr, 0/3] Support 64-bit (long) double 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 [this message]
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
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=5E136A67.5010301@gjlay.de \
--to=avr@gjlay.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.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).