public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47633] Result of COMPILER_VERSION() has NULL byte appended
Date: Sun, 13 Feb 2011 00:51:00 -0000	[thread overview]
Message-ID: <bug-47633-4-ahocGNh6CD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47633-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47633

--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-02-13 00:05:09 UTC ---
On Sat, Feb 12, 2011 at 11:29:47PM +0000, tkoenig at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47633
> 
> Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |tkoenig at gcc dot gnu.org
> 
> --- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2011-02-12 23:29:25 UTC ---
> (In reply to comment #4)
> > The testcase is bad, because for vanilla gcc releases there is no (prerelease)
> > etc. string at all (DEV-PHASE is empty), and because it hardcodes ASCII values,
> > so I'm afraid it could fail on EBCDIC or other targets.
> 
> I don't think gfortran supports EBCDIC very well right now.  At least
> the LLE and other functions don't take this into account.
> 

These functions specifically assume ascii.  For Fortran 2003:

  The intrinsic functions LGT, LGE, LLE, and LLT (13.7.63-13.7.66)
  provide comparisons between strings based on the ASCII collating
  sequence.  International portability is guaranteed if the set of
  characters used is limited to the letters, digits, underscore,
  and special characters.

See also Note 4.15:

  The intrinsic functions ACHAR (13.7.2) and IACHAR (13.7.45)
  provide conversion between characters and corresponding
  integer values according to the ASCII collating sequence.


  parent reply	other threads:[~2011-02-13  0:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 13:42 [Bug fortran/47633] New: " thenlich at users dot sourceforge.net
2011-02-07 16:12 ` [Bug fortran/47633] " kargl at gcc dot gnu.org
2011-02-07 16:20 ` jakub at gcc dot gnu.org
2011-02-07 17:49 ` sgk at troutmask dot apl.washington.edu
2011-02-07 18:10 ` jakub at gcc dot gnu.org
2011-02-07 19:13 ` burnus at gcc dot gnu.org
2011-02-07 19:37 ` sgk at troutmask dot apl.washington.edu
2011-02-13  0:05 ` tkoenig at gcc dot gnu.org
2011-02-13  0:51 ` sgk at troutmask dot apl.washington.edu [this message]
2011-02-14 17:25 ` burnus at gcc dot gnu.org
2011-02-15 19:39 ` kargl at gcc dot gnu.org
2011-02-15 19:46 ` kargl 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=bug-47633-4-ahocGNh6CD@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).