public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/114827] Valgrind reports errors with class(*) assignment Date: Sun, 28 Apr 2024 20:37:59 +0000 [thread overview] Message-ID: <bug-114827-4-YORAezr0cJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114827-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114827 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #58048|0 |1 is obsolete| | Attachment #58056|0 |1 is obsolete| | Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot gnu.org --- Comment #9 from anlauf at gcc dot gnu.org --- Created attachment 58061 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58061&action=edit Corrected patch This fixes the issue for scalar and array assignments and does not regress on intrinsic types when compiling with -fsanitize=address.
next prev parent reply other threads:[~2024-04-28 20:38 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-23 17:22 [Bug fortran/114827] New: " neil.n.carlson at gmail dot com 2024-04-23 17:24 ` [Bug fortran/114827] " neil.n.carlson at gmail dot com 2024-04-24 3:16 ` jvdelisle at gcc dot gnu.org 2024-04-24 13:19 ` neil.n.carlson at gmail dot com 2024-04-24 15:07 ` neil.n.carlson at gmail dot com 2024-04-24 19:47 ` anlauf at gcc dot gnu.org 2024-04-25 18:43 ` neil.n.carlson at gmail dot com 2024-04-26 19:33 ` anlauf at gcc dot gnu.org 2024-04-27 19:44 ` anlauf at gcc dot gnu.org 2024-04-28 20:37 ` anlauf at gcc dot gnu.org [this message] 2024-04-28 22:37 ` neil.n.carlson at gmail dot com 2024-04-29 18:39 ` anlauf at gcc dot gnu.org 2024-05-05 18:35 ` cvs-commit at gcc dot gnu.org 2024-05-09 18:30 ` cvs-commit at gcc dot gnu.org
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-114827-4-YORAezr0cJ@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: linkBe 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).