public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c/5025: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A
@ 2001-12-05 20:26 rodrigc
  0 siblings, 0 replies; 3+ messages in thread
From: rodrigc @ 2001-12-05 20:26 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR c/5025; it has been noted by GNATS.

From: rodrigc@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
  nobody@gcc.gnu.org, ssamant@lucent.com
Cc:  
Subject: Re: c/5025: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A
Date: 6 Dec 2001 04:18:07 -0000

 Synopsis: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A
 
 State-Changed-From-To: open->closed
 State-Changed-By: rodrigc
 State-Changed-When: Wed Dec  5 20:18:07 2001
 State-Changed-Why:
     This is not a bug with the compiler.
     Take this issue up with the vendor of your
     standard C library, ie. Sun.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5025&database=gcc


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: c/5025: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A
@ 2001-12-05 20:18 rodrigc
  0 siblings, 0 replies; 3+ messages in thread
From: rodrigc @ 2001-12-05 20:18 UTC (permalink / raw)
  To: gcc-bugs, gcc-gnats, gcc-prs, nobody, ssamant

Synopsis: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A

State-Changed-From-To: open->closed
State-Changed-By: rodrigc
State-Changed-When: Wed Dec  5 20:18:07 2001
State-Changed-Why:
    This is not a bug with the compiler.
    Take this issue up with the vendor of your
    standard C library, ie. Sun.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5025&database=gcc


^ permalink raw reply	[flat|nested] 3+ messages in thread

* c/5025: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A
@ 2001-12-05 17:36 ssamant
  0 siblings, 0 replies; 3+ messages in thread
From: ssamant @ 2001-12-05 17:36 UTC (permalink / raw)
  To: gcc-gnats


>Number:         5025
>Category:       c
>Synopsis:       gcc bug - read() and fread() treats carriage return to have hex value of 0x0A
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 05 17:36:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Shrinivas Samant
>Release:        gcc 2.7.2.3
>Organization:
>Environment:
Sun
>Description:
I create a file called 'input' letter 'a' and carriage return and line feed. When I do a checksum on this file, i get a result of 61+0A+0A = 0x75. But the expected answer is 0x61+0x0D+0x0A = 0x78. 
Why is the read() function treating a carriage return as 0x0a?
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-12-06  4:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-05 20:26 c/5025: gcc bug - read() and fread() treats carriage return to have hex value of 0x0A rodrigc
  -- strict thread matches above, loose matches on Subject: below --
2001-12-05 20:18 rodrigc
2001-12-05 17:36 ssamant

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).