public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/108192] g++.dg/cet-notrack-1.C searching for wrong function on mingw Date: Sat, 28 Jan 2023 16:32:20 +0000 [thread overview] Message-ID: <bug-108192-4-iFmMcTocVb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108192 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Yong <jyong@gcc.gnu.org>: https://gcc.gnu.org/g:6464409b0c7077e36858989b5dae302e2d26f45a commit r13-5475-g6464409b0c7077e36858989b5dae302e2d26f45a Author: Jonathan Yong <10walls@gmail.com> Date: Wed Jan 11 09:51:02 2023 +0000 PR c/108192 - Fix test for mingw gcc/testsuite/ChangeLog: PR c/108192 * g++.dg/cet-notrack-1.C: Use puts instead of printf, so function call is not mangled by __mingw_printf when doing assembly symbol inspection. Signed-off-by: Jonathan Yong <10walls@gmail.com>
next prev parent reply other threads:[~2023-01-28 16:32 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-21 5:14 [Bug testsuite/108192] New: " nightstrike at gmail dot com 2022-12-21 18:06 ` [Bug testsuite/108192] " hjl.tools at gmail dot com 2022-12-21 23:29 ` nightstrike at gmail dot com 2023-01-07 10:05 ` nightstrike at gmail dot com 2023-01-08 1:36 ` 10walls at gmail dot com 2023-01-08 1:38 ` pinskia at gcc dot gnu.org 2023-01-28 16:32 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-18 2:20 ` jyong 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-108192-4-iFmMcTocVb@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).