public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gabriel.torres at ll dot mit.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/110579] O2, O1 opmtimizations cause a buffer overflow panic during a strcpy
Date: Thu, 06 Jul 2023 20:54:33 +0000 [thread overview]
Message-ID: <bug-110579-4-oSZU7UbXaD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110579-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110579
--- Comment #5 from Gabriel <gabriel.torres at ll dot mit.edu> ---
I see. That makes sense.
Our research project has a dataset with tar 1.14. Our plan is to compare our
work with existing work in the dataset and to be consistent, use tar 1.14. We
noticed our binary compiled with gcc would abort when creating an archive while
using clang was fine.
prev parent reply other threads:[~2023-07-06 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 20:14 [Bug c/110579] New: " gabriel.torres at ll dot mit.edu
2023-07-06 20:14 ` [Bug c/110579] " gabriel.torres at ll dot mit.edu
2023-07-06 20:35 ` [Bug tree-optimization/110579] " sjames at gcc dot gnu.org
2023-07-06 20:41 ` pinskia at gcc dot gnu.org
2023-07-06 20:45 ` pinskia at gcc dot gnu.org
2023-07-06 20:54 ` gabriel.torres at ll dot mit.edu [this message]
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=bug-110579-4-oSZU7UbXaD@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).