public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "slyich at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug sim/29184] [PATCH] sim fails to build on 32-bit systems with -Werror=format-security Date: Mon, 06 Jun 2022 06:29:35 +0000 [thread overview] Message-ID: <bug-29184-4717-VZd9esYjdH@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29184-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29184 --- Comment #3 from Sergei Trofimovich <slyich at gmail dot com> --- It was posted to gdb-patches on May 21 as https://sourceware.org/pipermail/gdb-patches/2022-May/189288.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-06 6:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-25 21:14 [Bug sim/29184] New: " slyich at gmail dot com 2022-05-25 21:15 ` [Bug sim/29184] " slyich at gmail dot com 2022-06-06 5:00 ` vapier at gentoo dot org 2022-06-06 6:29 ` slyich at gmail dot com [this message] 2022-06-15 22:16 ` slyich at gmail dot com
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-29184-4717-VZd9esYjdH@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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).