public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Ioannis Papadopoulos <Ioannis.Papadopoulos@cern.ch>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/8655: Problematic behaviour of std::ends
Date: Thu, 28 Nov 2002 14:49:00 -0000	[thread overview]
Message-ID: <20021120160604.27916.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/8655; it has been noted by GNATS.

From: Ioannis Papadopoulos <Ioannis.Papadopoulos@cern.ch>
To: reichelt@igpm.rwth-aachen.de, <Ioannis.Papadopoulos@cern.ch>,
   <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <nobody@gcc.gnu.org>,
   <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: libstdc++/8655: Problematic behaviour of std::ends
Date: Wed, 20 Nov 2002 17:05:16 +0100 (CET)

 Hello,
 
 this problems appears on:
 
 1) Redhat Linux 7.2 and 7.3
 Output of gcc -v:
 
 Reading specs from 
 /usr/local/gcc-alt-3.2/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
 Configured with: ./configure --prefix=/usr/local/gcc-alt-3.2 --enable-shared
 Thread model: posix
 gcc version 3.2
 
 2) SuSE Linuz 8.0
 Output of gcc -v:
   
 Reading specs from 
 /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
 Configured with: /root/gcc-3.2/configure 
 Thread model: posix
 gcc version 3.2
 
 >     Are you really sure, you don't get the null charachter?
 >     Nedit displays it as "<soh>" and emacs as "^@".
 
 This is exactly what I get, and this is my problem!
 Moreover the C-string is always terminated at the first such character, as 
 the output of the example code shows:
 
 String size = 6
 C-string size = 5
 i = 1
 i = 1
 2nd string size = 9
 2nd C-string size = 5
 i = 1_1
 i = 1
 
 This behaviour did not exist on earlier versions of gcc, eg. 2.95.x
 
 Kind regards,
 Ioannis.
 
 
 On 20 Nov 2002 reichelt@igpm.rwth-aachen.de wrote:
 
 > Synopsis: Problematic behaviour of std::ends
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: reichelt
 > State-Changed-When: Wed Nov 20 05:57:08 2002
 > State-Changed-Why:
 >     I can't reproduce your problem with gcc 3.2 on i686-pc-linux-gnu.
 >     However, you did not specify the exact system configuration
 >     (output of gcc -v) and whether any optimization was used or
 >     not.
 >     
 >     Are you really sure, you don't get the null charachter?
 >     Nedit displays it as "<soh>" and emacs as "^@".
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8655
 > 
 
 -- 
 _____________________________________________________________________
 Ioannis PAPADOPOULOS  European Laboratory for Particle Physics (CERN)
                       IT Division, Geneva 23, CH-1211 Switzerland
                       office: 513-R-042, mailbox: G09100
                       tel:(+41 22 76) 74672, fax:(+41 22 76) 76830              
                       e-mail: Ioannis.Papadopoulos@cern.ch
                       URL: http://cern.ch/Ioannis.Papadopoulos
 


             reply	other threads:[~2002-11-20 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 14:49 Ioannis Papadopoulos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29  0:10 paolo
2002-11-28 15:03 Wolfgang Bangerth
2002-11-28 11:16 reichelt
2002-11-28  9:06 paolo
2002-11-28  8:26 Ioannis Papadopoulos
2002-11-28  8:19 paolo
2002-11-28  7:14 Ioannis.Papadopoulos

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=20021120160604.27916.qmail@sources.redhat.com \
    --to=ioannis.papadopoulos@cern.ch \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).