public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56581] Segfault when reading source file which starts with a byte-order mark (-cpp works)
Date: Mon, 11 Mar 2013 10:51:00 -0000 [thread overview]
Message-ID: <bug-56581-4-v51guRc2Ot@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56581-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56581
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
Summary|seg fault |Segfault when reading
| |source file which starts
| |with a byte-order mark
| |(-cpp works)
Ever Confirmed|1 |0
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-03-11 10:51:32 UTC ---
For completeness, the first line of the attachment starts with (od -x):
0000000 bbef 43bf 2020 2020 2020 2020 2020 2020
EF BB BF is the byte-order mark. (Followed by "C" and " ".)
It works if one uses "-cpp" as, seemingly, libcpp supports this. I think we
should consider supporting those BOM.
next prev parent reply other threads:[~2013-03-11 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 20:43 [Bug fortran/56581] New: seg fault walt.brainerd at gmail dot com
2013-03-10 12:23 ` [Bug fortran/56581] " tkoenig at gcc dot gnu.org
2013-03-10 16:03 ` walt.brainerd at gmail dot com
2013-03-10 16:29 ` tkoenig at gcc dot gnu.org
2013-03-10 19:25 ` burnus at gcc dot gnu.org
2013-03-10 19:39 ` walt.brainerd at gmail dot com
2013-03-11 10:18 ` rguenth at gcc dot gnu.org
2013-03-11 10:51 ` burnus at gcc dot gnu.org [this message]
2013-03-12 22:05 ` [Bug fortran/56581] Segfault when reading source file which starts with a byte-order mark (-cpp works) tkoenig at gcc dot gnu.org
2013-03-13 16:13 ` walt.brainerd at gmail dot com
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=bug-56581-4-v51guRc2Ot@http.gcc.gnu.org/bugzilla/ \
--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).