This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: may be undefined operation warning

From: "Diego Novillo" <dnovillo at google dot com>
To: "Wesley Smith" <wesley dot hoke at gmail dot com>
Cc: gcc-help at gcc dot gnu dot org
Date: Sun, 24 Feb 2008 23:08:12 -0500
Subject: Re: may be undefined operation warning
References: <1079b050802241931j22861fbft74aca2b478d6d0d2@mail.gmail.com> <b798aad50802242000l5b3cb0a6pbc99e1e47efe0d77@mail.gmail.com> <1079b050802242004t6bdcffc0uc1f5f15f7e4c745b@mail.gmail.com>

On Sun, Feb 24, 2008 at 23:04, Wesley Smith <wesley.hoke@gmail.com> wrote:

>  Thanks,
>  Perhaps I should have mentioned that before this is called (which is
>  in a tight for loop), I zero out the entire block of memory.

You have to post the exact code that's producing the warning.
Otherwise, it's impossible to help you.

Diego.

Follow-Ups:
- Re: may be undefined operation warning
  - From: Wesley Smith

References:
- may be undefined operation warning
  - From: Wesley Smith
- Re: may be undefined operation warning
  - From: Diego Novillo
- Re: may be undefined operation warning
  - From: Wesley Smith

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]