public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/17005] wide character strings don't work on HP-UX 11i using gcc 3.4.1
Date: Sun, 22 Aug 2004 17:35:00 -0000 [thread overview]
Message-ID: <20040822173522.6536.qmail@sourceware.org> (raw)
In-Reply-To: <20040812163817.17005.jerrydy@sbcglobal.net>
------- Additional Comments From pcarlini at suse dot de 2004-08-22 17:35 -------
Subject: Re: wide character strings don't work on HP-UX
11i using gcc 3.4.1
John David Anglin wrote:
>This is a work in progress. In one sense, the patch is complete
>except for documenting the -munix= option.
>
First, thanks for your work: if I understand well, on 11.11, and default
for -munix, we have obtained a clean wchar_t testsuite: great!
> However, it's dangerous
>to use other than default for this option.
>
>
Unfortunately, I have trouble understanding the details of your concerns:
hopefully, someone else will give you more meaningful advice. My naive
impression is that the new, documented, default, cannot be really dangerous,
by itself and the same for well documented new options. Also, if I
understand well, those options (93, 95, that is) can only lead to a behavior
similar to what we had before your patch... On the other hand, if this is
not the case, in my opinion you could work on adding that possibility.
Thanks again,
Paolo.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17005
next prev parent reply other threads:[~2004-08-22 17:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 16:38 [Bug c++/17005] New: " jerrydy at sbcglobal dot net
2004-08-12 17:23 ` [Bug c++/17005] " pcarlini at suse dot de
2004-08-12 17:26 ` [Bug libstdc++/17005] " pcarlini at suse dot de
2004-08-12 17:39 ` jbuck at gcc dot gnu dot org
2004-08-12 17:53 ` jbuck at gcc dot gnu dot org
2004-08-12 18:10 ` pcarlini at suse dot de
2004-08-12 18:29 ` jerrydy at sbcglobal dot net
2004-08-12 18:33 ` jbuck at gcc dot gnu dot org
2004-08-12 20:29 ` jerrydy at sbcglobal dot net
2004-08-12 22:09 ` danglin at gcc dot gnu dot org
2004-08-13 2:11 ` jerrydy at sbcglobal dot net
2004-08-13 4:40 ` danglin at gcc dot gnu dot org
2004-08-14 18:16 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-14 18:31 ` pcarlini at suse dot de
2004-08-14 19:03 ` cvs-commit at gcc dot gnu dot org
2004-08-14 19:27 ` pinskia at gcc dot gnu dot org
2004-08-14 19:45 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-15 18:06 ` pcarlini at suse dot de
2004-08-15 19:53 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-15 20:06 ` pcarlini at suse dot de
2004-08-15 20:47 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-15 22:29 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-21 10:26 ` pcarlini at suse dot de
2004-08-22 17:35 ` pcarlini at suse dot de [this message]
2004-08-22 19:31 ` dave at hiauly1 dot hia dot nrc dot ca
2004-08-25 17:50 ` cvs-commit at gcc dot gnu dot org
2004-08-25 18:08 ` pinskia at gcc dot gnu dot org
2005-01-31 16:39 ` pcarlini at suse dot de
2005-02-02 13:26 ` hundertmarck at boehme-weihs dot de
2005-02-02 13:30 ` pcarlini at suse dot de
2005-02-02 15:28 ` dave at hiauly1 dot hia dot nrc dot ca
2005-02-08 19:58 ` hundertmarck at boehme-weihs dot de
2005-03-01 10:43 ` hundertmarck at boehme-weihs dot de
2005-03-01 11:01 ` pcarlini at suse dot de
2005-03-01 11:12 ` hundertmarck at boehme-weihs dot de
2005-03-01 15:06 ` dave at hiauly1 dot hia dot nrc dot ca
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=20040822173522.6536.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).