From: "José Luis García Pallero" <jgpallero@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Warning using -Wconversion and -Ox in gcc 4.5 and 4.6 but not in previous releases
Date: Sun, 05 Jun 2011 16:03:00 -0000 [thread overview]
Message-ID: <BANLkTin+=7qRBmXTxs37o+TwPZswPpEgXQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1106051608310.6553@laptop-mg.saclay.inria.fr>
El día 5 de junio de 2011 16:17, Marc Glisse <marc.glisse@inria.fr> escribió:
> On Sun, 5 Jun 2011, José Luis García Pallero wrote:
>
>> Hello,
>> Three months ago I sent this mail to gcc-help:
>>
>> http://gcc.gnu.org/ml/gcc-help/2011-03/msg00064.html
>>
>> The behavior in gcc 4.6 release persists. I don't know if it is a bug
>> exactly (in the original mail, some says that is a bug and some no).
>
> There is no shame in filing a bug report without being absolutely certain.
>
> In this case you could file one for gcc asking to improve the warning
> (casting the constant 0 won't change its sign...), and one against glibc
> asking that they explicitly cast 0 to size_t, after looking a bit if you can
> find anything similar already reported. I am not saying either change will
> happen, but it seems like a resonable strategy. And you may get interesting
> comments on the bug reports.
But the warning is about the strspn() function instead of return 0; sentence
--
*****************************************
José Luis García Pallero
jgpallero@gmail.com
(o<
/ / \
V_/_
Use Debian GNU/Linux and enjoy!
*****************************************
next prev parent reply other threads:[~2011-06-05 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-05 14:25 José Luis García Pallero
2011-06-05 14:45 ` Marc Glisse
2011-06-05 16:03 ` José Luis García Pallero [this message]
2011-06-06 0:17 ` Marc Glisse
2011-06-06 10:01 ` Ian Lance Taylor
-- strict thread matches above, loose matches on Subject: below --
2011-03-07 10:07 José Luis García Pallero
2011-03-07 13:16 ` Marc Glisse
2011-03-07 14:20 ` José Luis García Pallero
2011-03-07 14:28 ` Cedric Roux
2011-03-07 22:02 ` José Luis García Pallero
2011-03-08 0:41 ` Ian Lance Taylor
2011-03-08 7:30 ` José Luis García Pallero
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='BANLkTin+=7qRBmXTxs37o+TwPZswPpEgXQ@mail.gmail.com' \
--to=jgpallero@gmail.com \
--cc=gcc-help@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).