public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ehrhardt@mathematik.uni-ulm.de
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/8449: Ellipsis in 3...5 not recognized properly
Date: Mon, 04 Nov 2002 08:26:00 -0000	[thread overview]
Message-ID: <20021104162425.31121.qmail@sources.redhat.com> (raw)


>Number:         8449
>Category:       preprocessor
>Synopsis:       Ellipsis in 3...5 not recognized properly
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 04 08:26:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Christian Ehrhardt
>Release:        gcc-3.2
>Organization:
>Environment:
Reading specs from /usr/local/bin/../lib/gcc-lib/sparc-sun-solaris2.9/3.2/specs
Configured with: /export/local/manager/playground/ULMgcc32/src/gcc-3.2/configure --with-ld=/usr/local/bin/ld --with-gnu-ld --with-as=/usr/local/bin/as --with-gnu-as --prefix=/usr/local/
Thread model: posix
gcc version 3.2
SunOS perseus 5.9 Generic_112233-01 sun4u sparc SUNW,Ultra-5_10
>Description:
Compiling this:

int a[2] = {[0 ...1]=1};

with gcc -c t.c gives an error:
gcc -c t9.c
t9.c:1: too many decimal points in floating constant
The cause is quite obious: The ellipsis is parsed as part of the
number. Something along these lines might fix it (only compile tested
as of yet)

--- cpplex.c.old	Mon Nov  4 17:15:08 2002
+++ cpplex.c	Mon Nov  4 17:14:45 2002
@@ -527,6 +527,7 @@
 {
   cpp_buffer *buffer = pfile->buffer;
   unsigned char *dest, *limit;
+  int dotdot = 0;
 
   dest = BUFF_FRONT (pfile->u_buff);
   limit = BUFF_LIMIT (pfile->u_buff);
@@ -547,6 +548,11 @@
     {
       do
 	{
+	  /* Is this potentially an ellipsis? */
+	  if (c == '.' && *(buffer->cur+1) == '.') {
+	    dotdot = 1;
+	    break;
+	  }
 	  /* Need room for terminating null.  */
 	  if ((size_t) (limit - dest) < 2)
 	    {
@@ -563,6 +569,8 @@
 
       /* Potential escaped newline?  */
       buffer->backup_to = buffer->cur - 1;
+      if (dotdot)
+        break;
       if (c != '?' && c != '\\')
 	break;
       c = skip_escaped_newlines (pfile);
>How-To-Repeat:
See above.
>Fix:
Add a space before the ellipsis.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-11-04 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04  8:26 ehrhardt [this message]
2002-11-04  8:56 Christian Ehrhardt
2002-11-07  0:26 Neil Booth
2002-11-07  1:26 Christian Ehrhardt
2002-11-07  3:16 Andreas Schwab
2002-11-07  3:38 neil

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=20021104162425.31121.qmail@sources.redhat.com \
    --to=ehrhardt@mathematik.uni-ulm.de \
    --cc=gcc-gnats@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: link
Be 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).