From: Harris Snyder <hsnyder@structura.bio>
To: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: Bug fix in ISO_Fortran_binding - unsigned char arrays
Date: Wed, 13 Jan 2021 01:34:44 -0500 [thread overview]
Message-ID: <8D9008DE-BC31-42DA-AFAD-EF665920E20A@structura.bio> (raw)
In-Reply-To: <CAFWzjBLmfKNx-g_Yrn8MJzu4P-aM_5+8oemFJCj2_CC_vW0azw@mail.gmail.com>
Hi everyone,
Sorry, my previous email erroneously referred to unsigned chars / uint8_t, when I in fact meant signed chars / int8_t. The actual patch works, but the test case files have ‘unit’ in the file names. I’ll provide a corrected patch tomorrow to fix the file names.
Harris
next prev parent reply other threads:[~2021-01-13 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 22:17 Possible bug re: ISO_Fortran_binding.h Harris Snyder
2021-01-11 11:24 ` Tobias Burnus
2021-01-11 15:42 ` Harris Snyder
2021-01-11 16:21 ` Tobias Burnus
2021-01-11 18:18 ` Harris Snyder
2021-01-12 14:30 ` Tobias Burnus
2021-01-12 19:20 ` [PATCH, Fortran] Bug fix in ISO_Fortran_binding - unsigned char arrays Harris Snyder
2021-01-13 6:34 ` Harris Snyder [this message]
2021-01-13 16:02 ` [PATCH, Fortran] PR fortran/93524 - ISO_Fortran_binding signed " Harris Snyder
2021-01-14 3:42 ` Jerry DeLisle
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=8D9008DE-BC31-42DA-AFAD-EF665920E20A@structura.bio \
--to=hsnyder@structura.bio \
--cc=fortran@gcc.gnu.org \
--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).