From: Jerry DeLisle <jvdelisle@charter.net>
To: dhumieres.dominique@free.fr
Cc: sgk@troutmask.apl.washington.edu, fortran@gcc.gnu.org,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: off-by-one buffer overflow patch
Date: Sat, 27 Mar 2021 15:11:05 -0700 [thread overview]
Message-ID: <a3c6fb47-411c-dc46-4fcb-f727b6cae226@charter.net> (raw)
In-Reply-To: <0710b0f9f5f317e0ba8bff6de5391bdf@free.fr>
Pushed:
To git+ssh://gcc.gnu.org/git/gcc.git
651684b462f..01685676a93 master -> master
Author: Steve Kargl <kargl@gcc.gnu.org>
Date: Sat Mar 27 15:02:16 2021 -0700
fortran: Fix off-by-one in buffer sizes.
gcc/fortran/ChangeLog:
* misc.c (gfc_typename): Fix off-by-one in buffer sizes.
Regards,
Jerry
On 3/27/21 6:28 AM, dhumieres.dominique@free.fr wrote:
> Le 2021-03-27 06:36, Jerry DeLisle a écrit :
>> On 3/26/21 10:38 AM, dhumieres.dominique--- via Fortran wrote:
>>> I have proposed a similar patch in pr95998.
>>>
>>> I cannot commit to git!-(
>>>
>>> Thanks
>>>
>>> Dominique
>> I do not see a patch in 95998. Do you need help to do a commit?
>>
>> Jerry
>
> I was too quick and did not realize that I did not post the actual patch
> I have in my working tree, but the Steve's one does the trick.
>
> And yes I need help to do a commit.
>
> Thanks
>
> Dominique
next prev parent reply other threads:[~2021-03-27 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 17:38 dhumieres.dominique
2021-03-27 5:36 ` Jerry DeLisle
2021-03-27 13:28 ` dhumieres.dominique
2021-03-27 22:11 ` Jerry DeLisle [this message]
2021-03-27 23:49 ` Steve Kargl
-- strict thread matches above, loose matches on Subject: below --
2021-03-26 17:29 Steve Kargl
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=a3c6fb47-411c-dc46-4fcb-f727b6cae226@charter.net \
--to=jvdelisle@charter.net \
--cc=dhumieres.dominique@free.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).