public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/3885] Incorrect "invalid suffix on integer constant" error Date: Mon, 20 Jun 2022 20:31:47 +0000 [thread overview] Message-ID: <bug-3885-4-PWa0tw2Hz5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-3885-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3885 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |j at uriah dot heep.sax.de --- Comment #16 from Andrew Pinski <pinskia at gcc dot gnu.org> --- *** Bug 33547 has been marked as a duplicate of this bug. ***
next prev parent reply other threads:[~2022-06-20 20:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-3885-4@http.gcc.gnu.org/bugzilla/> 2011-01-30 8:10 ` pinskia at gcc dot gnu.org 2012-09-15 12:03 ` schwab@linux-m68k.org 2014-09-22 5:13 ` pinskia at gcc dot gnu.org 2014-09-22 5:13 ` pinskia at gcc dot gnu.org 2022-06-20 20:30 ` pavel.morozkin at gmail dot com 2022-06-20 20:31 ` pinskia at gcc dot gnu.org [this message] 2022-06-20 20:31 ` pinskia at gcc dot gnu.org [not found] <bug-3885-1151@http.gcc.gnu.org/bugzilla/> 2009-12-18 1:23 ` pinskia at gcc dot gnu dot org 2009-12-18 1:24 ` pinskia at gcc dot gnu dot org 2009-12-18 1:25 ` pinskia at gcc dot gnu dot org [not found] <20010730145600.3885.keith.rollin@corp.palm.com> 2003-12-09 13:03 ` skghosh at linuxmail dot org 2003-12-09 18:19 ` zack at gcc dot gnu 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-3885-4-PWa0tw2Hz5@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).