public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "geoffk at geoffk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/13361] const wchar_t * strings not stored in pch
Date: Sat, 19 Jun 2004 00:11:00 -0000 [thread overview]
Message-ID: <20040619001100.1003.qmail@sourceware.org> (raw)
In-Reply-To: <20031208214209.13361.thomas.francis@pkware.com>
------- Additional Comments From geoffk at geoffk dot org 2004-06-19 00:10 -------
Subject: Re: const wchar_t * strings not stored in pch
On 18/06/2004, at 4:45 PM, mmitchel at gcc dot gnu dot org wrote:
> Postponed until GCC 3.4.2.
>
> Geoff, it would be nice if you would help Rainer solve this problem.
> We
> shouldn't have to choose between supporting that platform and having
> PCH that
> works with wide-character literals, and it's going to be really hard
> for him to
> work this out by himself.
I believe that this is a problem in the Alpha backend (which I don't
know much about) or in the system C library on Tru64 (which I know
nothing at all about, and don't have access to); and exposing it
requires building Ada (which I can't do, and don't know about) on Tru64
(which I don't have access to). But given those constraints, I'd be
happy to give any help I can.
I'd suggest, though, that if we want to support Ada on Tru64-alpha,
that we should have someone who *does* have access to the platform and
*can* solve problems like these.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13361
next prev parent reply other threads:[~2004-06-19 0:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 21:42 [Bug pch/13361] New: " thomas dot francis at pkware dot com
2003-12-08 23:02 ` [Bug pch/13361] " pinskia at gcc dot gnu dot org
2003-12-09 7:46 ` pinskia at gcc dot gnu dot org
2003-12-19 11:32 ` pinskia at gcc dot gnu dot org
2004-01-12 23:18 ` geoffk at gcc dot gnu dot org
2004-01-15 17:32 ` geoffk at gcc dot gnu dot org
2004-01-16 7:20 ` cvs-commit at gcc dot gnu dot org
2004-01-16 7:22 ` geoffk at gcc dot gnu dot org
2004-01-16 7:23 ` geoffk at gcc dot gnu dot org
2004-01-27 13:07 ` cvs-commit at gcc dot gnu dot org
2004-02-05 21:56 ` cvs-commit at gcc dot gnu dot org
2004-02-05 22:01 ` cvs-commit at gcc dot gnu dot org
2004-02-06 2:46 ` pinskia at gcc dot gnu dot org
2004-02-06 20:48 ` geoffk at gcc dot gnu dot org
2004-03-16 16:26 ` pinskia at gcc dot gnu dot org
2004-04-05 17:23 ` pinskia at gcc dot gnu dot org
2004-06-04 22:07 ` geoffk at gcc dot gnu dot org
2004-06-09 19:23 ` mmitchel at gcc dot gnu dot org
2004-06-09 19:31 ` ro at techfak dot uni-bielefeld dot de
2004-06-18 23:45 ` mmitchel at gcc dot gnu dot org
2004-06-19 0:11 ` geoffk at geoffk dot org [this message]
2004-08-29 17:57 ` mmitchel at gcc dot gnu dot org
2004-09-16 23:40 ` geoffk at gcc dot gnu dot org
2004-09-18 5:51 ` cvs-commit at gcc dot gnu dot org
2004-09-18 6:45 ` geoffk at gcc dot gnu dot 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=20040619001100.1003.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).