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/20109] printf optimizations and non-ASCII character sets
Date: Tue, 29 Nov 2005 05:18:00 -0000	[thread overview]
Message-ID: <20051129051801.26857.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20109-230@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from ghazi at gcc dot gnu dot org  2005-11-29 05:18 -------
Subject: Bug 20109

Author: ghazi
Date: Tue Nov 29 05:17:56 2005
New Revision: 107653

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107653
Log:
        PR middle-end/20109
        PR middle-end/25120
        * builtins.c (init_target_chars): New.
        (expand_builtin_printf, expand_builtin_fprintf,
        expand_builtin_sprintf, fold_builtin_sprintf,
        maybe_emit_sprintf_chk_warning, fold_builtin_sprintf_chk,
        fold_builtin_snprintf_chk, fold_builtin_printf,
        fold_builtin_fprintf): Check for matching format strings using
        the target charset.

testsuite:
        * gcc.dg/charset/builtin2.c: New test.


Added:
    branches/gcc-4_1-branch/gcc/testsuite/gcc.dg/charset/builtin2.c
Modified:
    branches/gcc-4_1-branch/gcc/ChangeLog
    branches/gcc-4_1-branch/gcc/builtins.c
    branches/gcc-4_1-branch/gcc/testsuite/ChangeLog


-- 


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


  parent reply	other threads:[~2005-11-29  5:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20109-230@http.gcc.gnu.org/bugzilla/>
2005-11-28  2:45 ` 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 [this message]
2005-11-29  5:18 ` ghazi at gcc dot gnu dot org
2005-02-21  2:41 [Bug middle-end/20109] New: " jsm28 at gcc dot gnu dot org
2005-02-22  0:13 ` [Bug middle-end/20109] " pinskia 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=20051129051801.26857.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).