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: Mon, 25 Feb 2008 08:34:56 -0500
Subject: Re: may be undefined operation warning
References: <1079b050802241931j22861fbft74aca2b478d6d0d2@mail.gmail.com> <b798aad50802242000l5b3cb0a6pbc99e1e47efe0d77@mail.gmail.com> <1079b050802242004t6bdcffc0uc1f5f15f7e4c745b@mail.gmail.com> <b798aad50802242008q39f71fafx8dacc435dea76c8b@mail.gmail.com> <1079b050802242009n6a53303dl3a1ca0e1ce4c099e@mail.gmail.com> <b798aad50802242021r3612529at17613dca334d193e@mail.gmail.com> <1079b050802242026j784cb4habd6e3f215606c30@mail.gmail.com>

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

>  Yes, it happens on the last line.  I'll need to make a simple C app
>  that shows the behavior to submit.  How does one make a .i file?

Use -save-temps.  http://gcc.gnu.org/bugs.html contains detailed
instructions to help you submit bug reports.

Diego.

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
- Re: may be undefined operation warning
  - From: Diego Novillo
- Re: 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]