public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: winter@alum.mit.edu
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/6489: tradcpp0 fails on line ending with '\r\n'
Date: Sat, 27 Apr 2002 10:26:00 -0000	[thread overview]
Message-ID: <20020427172248.9340.qmail@sources.redhat.com> (raw)


>Number:         6489
>Category:       preprocessor
>Synopsis:       tradcpp0 fails on line ending with '\r\n'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 27 10:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     winter@alum.mit.edu
>Release:        gcc-3.0.4
>Organization:
>Environment:
Athlon, Redhat 6.2, gcc-3.0.4 built/installed from source using
default configuration
>Description:
When g77 preprocesses a file (using tradcpp0), if it encounters
a line like 

  #include "fname"\r\n

it fails with the message

  #include expects "fname" or <fname>

Stepping through tradcpp0 with gdb reveals that it fails
to strip off the trailing \r (although it successfully handles
the \n) and thus concludes that the line is bogus.

Furthermore, manual removal of \r from the file (using 
for instance fromdos) "fixes" the problem.
>How-To-Repeat:
Replace any line of the form
  #include "fname"\n
with 
  #include "fname"\r\n
in a fortran source code and the problem should be repeatable.
>Fix:
Whatever code strips the trailing \n should also include
stripping of trailing \r\n combinations.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-27 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-27 10:26 winter [this message]
2002-05-03 13:41 jakub

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=20020427172248.9340.qmail@sources.redhat.com \
    --to=winter@alum.mit.edu \
    --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).