public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/31924] gcc accepts invalid suffixes for decimal float constants Date: Mon, 14 May 2007 23:43:00 -0000 [thread overview] Message-ID: <20070514234332.31661.qmail@sourceware.org> (raw) In-Reply-To: <bug-31924-4503@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from janis at gcc dot gnu dot org 2007-05-15 00:43 ------- Subject: Bug 31924 Author: janis Date: Mon May 14 23:43:07 2007 New Revision: 124730 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124730 Log: libcpp/ PR c/31924 * expr.c (interpret_float_suffix): Check for invalid suffix. gcc/testsuite/ PR c/31924 * gcc.dg/fltconst-1.c: New test. Added: trunk/gcc/testsuite/gcc.dg/fltconst-1.c Modified: trunk/gcc/testsuite/ChangeLog trunk/libcpp/ChangeLog trunk/libcpp/expr.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31924
next prev parent reply other threads:[~2007-05-14 23:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-14 20:50 [Bug c/31924] New: " janis at gcc dot gnu dot org 2007-05-14 23:43 ` janis at gcc dot gnu dot org [this message] 2007-05-21 21:17 ` [Bug c/31924] " janis at gcc dot gnu dot org 2007-06-24 3:49 ` pinskia 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=20070514234332.31661.qmail@sourceware.org \ --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).