From: Robin Dapp <rdapp.gcc@gmail.com>
To: Jivan Hakobyan <jivanhakobyan9@gmail.com>, gcc-patches@gcc.gnu.org
Cc: rdapp.gcc@gmail.com, Jeff Law <jlaw@ventanamicro.com>
Subject: Re: LTO: buffer overflow in lto_output_init_mode_table
Date: Thu, 22 Jun 2023 13:42:55 +0200 [thread overview]
Message-ID: <2a1e37bd-b41e-c4e1-877e-5dd608f3ca83@gmail.com> (raw)
In-Reply-To: <CAHso6sMRM9YmzmpuHTeMNAd1e2PKXkCkkkdnM1-M34YqGZ8b2w@mail.gmail.com>
Hi Jivan,
I think Pan is already on this problem. Please see this thread:
https://gcc.gnu.org/pipermail/gcc-patches/2023-June/622129.html
Regards
Robin
next prev parent reply other threads:[~2023-06-22 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 11:36 Jivan Hakobyan
2023-06-22 11:42 ` Robin Dapp [this message]
2023-06-22 12:36 ` Jivan Hakobyan
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=2a1e37bd-b41e-c4e1-877e-5dd608f3ca83@gmail.com \
--to=rdapp.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jivanhakobyan9@gmail.com \
--cc=jlaw@ventanamicro.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).