I saw the gcc.gnu.org at the end of the address and did not realize
the link was not part gnu.org.
The gcc.gnu.org link is:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564239.html
with the attachment at
https://gcc.gnu.org/pipermail/gcc-patches/attachments/20210125/b5a7df3b/attachment-
On Mon, 1 Feb 2021, Patrick McGehearty via Gcc-patches wrote:
> The message which contains the attached gzipped tarball of the
> development test programs is:
> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg254210.html
> I'll include that link in the new patch as well.
I think it's best
The message which contains the attached gzipped tarball of the
development test programs is:
https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg254210.html
I'll include that link in the new patch as well.
I can't recall why I did not use _LIBGCC_XF_EPSILON__ or
_LIBGCC_TF_EPSILON__ before. P
On Mon, 25 Jan 2021, Patrick McGehearty via Gcc-patches wrote:
> Anyway, once I created the tarball and gzipped it,
> I found it shrank to 100Kbytes. Rather than have further
> delays, I've attached the gzip file to this email.
Thanks. The next patch version can include the URL of this file in t
There are two open gcc bugzilla bugs for complex divide.
59714 complex divide is surprising on targets with FMA
60646 investigate improved complex division algorithms
Either might be appropriate. 59714 started my investigation,
and my solution resolves that issue, while my solution
seems closer t
On Mon, 25 Jan 2021, Patrick McGehearty wrote:
> On 1/21/2021 5:04 PM, Joseph Myers wrote:
> > On Fri, 18 Dec 2020, Patrick McGehearty via Gcc-patches wrote:
> >
> > > TEST Data
> > I'd still like to see the test data / code used to produce the accuracy
> > and performance results made available
On 1/21/2021 5:04 PM, Joseph Myers wrote:
On Fri, 18 Dec 2020, Patrick McGehearty via Gcc-patches wrote:
TEST Data
I'd still like to see the test data / code used to produce the accuracy
and performance results made available somewhere (presumably with a link
then being provided in the comm
On Fri, 18 Dec 2020, Patrick McGehearty via Gcc-patches wrote:
> TEST Data
I'd still like to see the test data / code used to produce the accuracy
and performance results made available somewhere (presumably with a link
then being provided in the commit message).
> + if ((mode == TYPE_MO
Ping.
With the holidays coming shortly after I posted this this on Dec 17, 2020,
I understand any delays in getting it reviewed. Still, I thought
I should give a ping.
I very much would like to complete this project while I can still
find all my notes related to the design decisions. :-)
- Pat
Changes in this version from Version 5:
Commit message change:
Information for Changelogs put in proper format. Thanks go to
Jakub Jelinek for enlightening me how to do that and providing
an excellent example.
c-cppbuiltin.c - Fixed various formatting issues regard
10 matches
Mail list logo
