public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41219] libgfortran build warnings
Date: Mon, 07 Sep 2009 02:57:00 -0000 [thread overview]
Message-ID: <20090907025719.987.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41219-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from jvdelisle at gcc dot gnu dot org 2009-09-07 02:57 -------
Regarding comment #6.
>> In write_a_char4, one has:
>> const char crlf[] = "\r\n";
>> write_default_char4 (dtp, crlf, 2, 0);
>> but the second argument should be gfc_char4_t*
>Right. So what is "\r\n" in terms of gfc_char4_t?
I believe the following is the correct fix for this. I have partially tested
this but need to do some more testing.
Index: write.c
===================================================================
--- write.c (revision 151441)
+++ write.c (working copy)
@@ -293,7 +293,7 @@
Standard sections 10.6.3 and 9.9 for further information. */
if (is_stream_io (dtp))
{
- const char crlf[] = "\r\n";
+ const gfc_char4_t crlf[] = {0x000d,0x000a};
int i, bytes;
gfc_char4_t *qq;
bytes = 0;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41219
next prev parent reply other threads:[~2009-09-07 2:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 21:09 [Bug fortran/41219] New: " burnus at gcc dot gnu dot org
2009-09-03 6:55 ` [Bug fortran/41219] " burnus at gcc dot gnu dot org
2009-09-03 7:12 ` burnus at gcc dot gnu dot org
2009-09-03 7:37 ` burnus at gcc dot gnu dot org
2009-09-03 8:36 ` ktietz at gcc dot gnu dot org
2009-09-04 9:25 ` burnus at gcc dot gnu dot org
2009-09-06 13:55 ` jb at gcc dot gnu dot org
2009-09-06 18:18 ` jvdelisle at gcc dot gnu dot org
2009-09-06 21:21 ` jvdelisle at gcc dot gnu dot org
2009-09-07 2:57 ` jvdelisle at gcc dot gnu dot org [this message]
2009-09-07 11:27 ` sezeroz at gmail dot com
2009-09-08 0:59 ` jvdelisle at gcc dot gnu dot org
2009-09-12 5:36 ` nightstrike at gmail dot com
2009-09-12 14:49 ` jvdelisle at gcc dot gnu dot org
2009-09-12 15:08 ` jvdelisle at gcc dot gnu dot org
2009-09-21 16:31 ` nightstrike at gmail dot com
2009-09-21 16:33 ` nightstrike at gmail dot com
2009-09-21 17:01 ` burnus at gcc dot gnu dot org
2009-09-21 17:36 ` nightstrike at gmail dot com
2009-09-21 18:01 ` kargl at gcc dot gnu dot org
2009-09-21 18:12 ` nightstrike at gmail dot com
2009-10-30 22:38 ` jb at gcc dot gnu dot org
2009-12-29 15:49 ` fxcoudert at gcc dot gnu dot org
2010-05-07 16:01 ` dfranke at gcc dot gnu dot org
2010-05-07 17:18 ` nightstrike at gmail dot com
2010-05-07 17:44 ` sezeroz at gmail dot com
[not found] <bug-41219-4@http.gcc.gnu.org/bugzilla/>
2010-10-14 1:30 ` jvdelisle at gcc dot gnu.org
2010-10-14 1:31 ` jvdelisle at gcc dot gnu.org
2010-11-01 22:31 ` jvdelisle at gcc dot gnu.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=20090907025719.987.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: 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).