public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: Nix <nix@esperi.org.uk>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	David Miller <davem@davemloft.net>,
	xiyou.wangcong@gmail.com, goodmenkernel@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: Is there any word about this bug in gcc ?
Date: Wed, 21 Nov 2007 21:19:05 +0500	[thread overview]
Message-ID: <47445A79.7020902@gmail.com> (raw)
In-Reply-To: <47442FA9.6020600@gmail.com>

I wrote:
> Nix wrote:
>> Possible hits (I'm not sure what the folder would do with this: the
>> extra level of brackets in the way might affect things but I don't think
>> so):
>>
>> ./libtheora/libtheora/lib/enc/pp.c:      TmpMod = 32 + QValue - 
>> 2*(abs(Src[j+Pitch]-Src[j]));
>> ./libtheora/libtheora/lib/enc/pp.c:      TmpMod = 32 + QValue - 
>> 2*(abs(Src[j+1]-Src[j]));
> 
> This did emit a warning, I have already reported it: 
> https://trac.xiph.org/ticket/1260

And on IRC, they explained that it is a piece of code that never gets called. So 
not a hit.

-- 
Alexander E. Patrakov

  reply	other threads:[~2007-11-21 16:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  2:13 Is there any word about this bug in gcc ? zhengyi
2007-11-20  4:16 ` WANG Cong
2007-11-20  5:10   ` H. Peter Anvin
2007-11-20  5:39     ` WANG Cong
2007-11-20  6:03       ` Li Zefan
2007-11-20  6:10         ` WANG Cong
2007-11-20  6:04       ` H. Peter Anvin
2007-11-20  6:17       ` David Miller
2007-11-20  6:41         ` Herbert Xu
2007-11-20  6:47           ` H. Peter Anvin
2007-11-20  6:52             ` Herbert Xu
2007-11-20 12:52               ` Alessandro Suardi
2007-11-20 18:42                 ` Sami Farin
2007-11-20 21:10             ` Nix
2007-11-21 13:16               ` Alexander E. Patrakov
2007-11-21 16:19                 ` Alexander E. Patrakov [this message]
2007-11-21 17:22                   ` Lennart Sorensen

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=47445A79.7020902@gmail.com \
    --to=patrakov@gmail.com \
    --cc=davem@davemloft.net \
    --cc=goodmenkernel@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    --cc=xiyou.wangcong@gmail.com \
    /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