public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/26021] gcc.c:3866: warning: comparison between signed and unsigned Date: Sun, 29 Jan 2006 23:29:00 -0000 [thread overview] Message-ID: <20060129232925.13285.qmail@sourceware.org> (raw) In-Reply-To: <bug-26021-276@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from danglin at gcc dot gnu dot org 2006-01-29 23:29 ------- It appears that this problem was exposed by: 2006-01-28 Zack Weinberg <zackw@panix.com> * c.opt: Add -W(no-)overlength-strings. * doc/invoke.texi: Document it. * c-opts.c (c_common_handle_option): -pedantic implies -Woverlength-strings, if not explicitly disabled already. (c_common_post_options): -Woverlength-strings defaults to off, and is always off for C++. * c-common.c (fix_string_type): Issue warning about strings longer than is portable only if warn_overlength_strings. Rearrange code a little for clarity. * configure.in: Check for -Wno-overlength-strings as well before enabling -pedantic in stage 1. * Makefile.in (STRICT2_WARN): Add -Wno-overlength-strings. (gcc.o-warn, insn-automata.o-warn, build/gencondmd.o-warn): Delete. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26021
next prev parent reply other threads:[~2006-01-29 23:29 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-01-29 23:13 [Bug driver/26021] New: " danglin at gcc dot gnu dot org 2006-01-29 23:29 ` danglin at gcc dot gnu dot org [this message] 2006-01-29 23:31 ` [Bug driver/26021] [4.2 Regression] " pinskia at gcc dot gnu dot org 2006-01-29 23:32 ` danglin at gcc dot gnu dot org 2006-01-30 0:41 ` pinskia at gcc dot gnu dot org 2006-01-31 1:04 ` dave at hiauly1 dot hia dot nrc dot ca 2006-02-02 0:09 ` sje at cup dot hp dot com 2006-02-02 1:12 ` 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=20060129232925.13285.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: linkBe 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).