public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/25120] builtin *printf handlers are confused by -fexec-charset
Date: Wed, 07 Dec 2005 03:54:00 -0000 [thread overview]
Message-ID: <20051207035437.10426.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25120-578@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from ghazi at gcc dot gnu dot org 2005-12-07 03:54 -------
(In reply to comment #12)
> Subject: Re: builtin *printf handlers are confused by -fexec-charset
> "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
> | Backporting this fix to 3.4 requires also backporting the infrastructure
> patch
> | for the lang hook to_target_charset posted here:
> | http://gcc.gnu.org/ml/gcc-patches/2005-02/msg00780.html
> Hmm, I'm tempted to leave it is as wontix on 3.4.x. Thoughts?
> -- Gaby
I'm inclined to agree. I'm not familiar with the to_target_charset code enough
that I feel comfortable backporting it to a stable release series. If someone
else wants to tackle that, (Joseph?) then I'll backport the fix for this bug
and the testsuite iconv support. But I won't touch the charset stuff myself in
3.4.
--Kaveh
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25120
next prev parent reply other threads:[~2005-12-07 3:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-27 15:50 [Bug middle-end/25120] New: [3.4/4.0/4.1/4.2] builtin printf/fprintf is " ghazi at gcc dot gnu dot org
2005-11-27 15:52 ` [Bug middle-end/25120] " ghazi at gcc dot gnu dot org
2005-11-27 16:11 ` [Bug middle-end/25120] " pinskia at gcc dot gnu dot org
2005-11-27 16:59 ` ghazi at gcc dot gnu dot org
2005-11-27 17:01 ` [Bug middle-end/25120] builtin *printf handlers are " ghazi at gcc dot gnu dot org
2005-11-27 22:45 ` ghazi at gcc dot gnu dot org
2005-11-28 0:45 ` joseph at codesourcery dot com
2005-11-28 2:45 ` ghazi at gcc dot gnu dot org
2005-11-28 3:36 ` ghazi at gcc dot gnu dot org
2005-11-29 5:17 ` ghazi at gcc dot gnu dot org
2005-11-29 5:18 ` ghazi at gcc dot gnu dot org
2005-11-29 5:18 ` ghazi at gcc dot gnu dot org
2005-12-04 16:23 ` ghazi at gcc dot gnu dot org
2005-12-04 17:07 ` gdr at integrable-solutions dot net
2005-12-07 3:54 ` ghazi at gcc dot gnu dot org [this message]
2006-02-05 21:40 ` pinskia at gcc dot gnu dot org
2006-09-16 16:32 ` kalium at gmx dot de
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=20051207035437.10426.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).