public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100907] Bind(c): failure handling wide character
Date: Fri, 22 Oct 2021 12:57:34 +0000	[thread overview]
Message-ID: <bug-100907-4-NqKIpUNi0O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100907-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100907

--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
In both case I get

FAIL! chrcmp: 66 != 65281
FAIL! chrcmp: 66 != 65281
FAIL! chrcmp: 67 != 65282
FAIL! chrcmp: 68 != 65283
FAIL! chrcmp: 69 != 65284
FAIL! chrcmp: 70 != 65285
FAIL! chrcmp: 71 != 65286
FAIL! chrcmp: 72 != 65287
FAIL! chrcmp: 73 != 65288
FAIL! chrcmp: 74 != 65289
FAIL! chrcmp: 75 != 65290
FAIL! chrcmp: 0 != 65291
FAIL! char: 75 != 11
Assertion failed: (c_vrfy_character (auxp)), function check_tk, file
pr100907_db.c, line 215.

Program received signal SIGABRT: Process abort signal.

      parent reply	other threads:[~2021-10-22 12:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 17:47 [Bug fortran/100907] New: " jrfsousa at gcc dot gnu.org
2021-06-04 17:47 ` [Bug fortran/100907] " jrfsousa at gcc dot gnu.org
2021-06-05 12:17 ` dominiq at lps dot ens.fr
2021-06-06  0:24 ` jrfsousa at gcc dot gnu.org
2021-06-06  0:24 ` jrfsousa at gcc dot gnu.org
2021-06-06 13:15 ` dominiq at lps dot ens.fr
2021-06-06 15:32 ` jrfsousa at gcc dot gnu.org
2021-06-13 18:50 ` jrfsousa at gcc dot gnu.org
2021-06-18 11:01 ` dominiq at lps dot ens.fr
2021-09-02 23:42 ` cvs-commit at gcc dot gnu.org
2021-10-21 23:26 ` sandra at gcc dot gnu.org
2021-10-22 12:44 ` burnus at gcc dot gnu.org
2021-10-22 12:57 ` dominiq at lps dot ens.fr [this message]

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-100907-4-NqKIpUNi0O@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).