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 libfortran/81985] several sanitizer undefined runtime errors in sanitized libgfortran Date: Wed, 17 May 2023 20:57:16 +0000 [thread overview] Message-ID: <bug-81985-4-8bauIwtDLX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-81985-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81985 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING --- Comment #3 from anlauf at gcc dot gnu.org --- I don't see the issue here anymore as we inline expand intrinsic MVBITS since gcc-11 and do no longer generate libgfortran calls. The issue might still exist in gcc-10. Shall we close this one as fixed?
next parent reply other threads:[~2023-05-17 20:57 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-81985-4@http.gcc.gnu.org/bugzilla/> 2023-05-17 20:57 ` anlauf at gcc dot gnu.org [this message] 2023-06-19 7:55 ` fxcoudert 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-81985-4-8bauIwtDLX@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).