public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uaa at mx5 dot nisiq.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug demangler/107884] H8/300: cp-demangle.c fix warning related demangle.h Date: Tue, 29 Nov 2022 12:29:13 +0000 [thread overview] Message-ID: <bug-107884-4-uatTqqFXEW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107884-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107884 --- Comment #6 from SASANO Takayoshi <uaa at mx5 dot nisiq.net> --- Created attachment 53980 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53980&action=edit rewrite int options -> int32_t options
next prev parent reply other threads:[~2022-11-29 12:29 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-26 23:16 [Bug libstdc++/107884] New: " uaa at mx5 dot nisiq.net 2022-11-27 0:19 ` [Bug demangler/107884] " pinskia at gcc dot gnu.org 2022-11-27 9:35 ` uaa at mx5 dot nisiq.net 2022-11-28 7:44 ` rguenth at gcc dot gnu.org 2022-11-28 9:13 ` redi at gcc dot gnu.org 2022-11-28 11:37 ` redi at gcc dot gnu.org 2022-11-29 12:29 ` uaa at mx5 dot nisiq.net [this message] 2023-01-05 13:56 ` redi at gcc dot gnu.org 2023-02-24 15:25 ` mike at mnmoran dot org 2023-02-24 15:30 ` mike at mnmoran dot org 2023-02-26 12:34 ` uaa at mx5 dot nisiq.net 2023-02-26 14:58 ` mike at mnmoran dot 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-107884-4-uatTqqFXEW@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).