Re: [Valgrind-users] gcc 4.6.0 - set but not used warnings

2011-03-30 Thread Bart Van Assche
On Tue, Mar 29, 2011 at 12:24 PM, Bart Van Assche bvanass...@acm.org wrote: On Mon, Mar 28, 2011 at 11:14 PM, Julian Seward jsew...@acm.org wrote: On Monday, March 28, 2011, Bart Van Assche wrote: On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward jsew...@acm.org wrote: On Monday, March 28,

Re: [Valgrind-users] gcc 4.6.0 - set but not used warnings

2011-03-28 Thread Julian Seward
On Monday, March 28, 2011, Piotr Jaroszyński wrote: I think the proper solution is to add __attribute__((unused)) to _qzz_res. What do you think? Yes. I just committed exactly such cleanups (r11673). Could you try it, to see if that also makes your compiles quiet again? J

Re: [Valgrind-users] gcc 4.6.0 - set but not used warnings

2011-03-28 Thread Bart Van Assche
On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward jsew...@acm.org wrote: On Monday, March 28, 2011, Piotr Jaroszyński wrote: I think the proper solution is to add __attribute__((unused)) to _qzz_res. What do you think? Yes.  I just committed exactly such cleanups (r11673).  Could you try it,

Re: [Valgrind-users] gcc 4.6.0 - set but not used warnings

2011-03-28 Thread Julian Seward
On Monday, March 28, 2011, Bart Van Assche wrote: On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward jsew...@acm.org wrote: On Monday, March 28, 2011, Piotr Jaroszyński wrote: I think the proper solution is to add __attribute__((unused)) to _qzz_res. What do you think? Yes. I just

Re: [Valgrind-users] gcc 4.6.0 - set but not used warnings

2011-03-28 Thread Julian Seward
On Monday, March 28, 2011, Bart Van Assche wrote: On Mon, Mar 28, 2011 at 6:32 PM, Julian Seward jsew...@acm.org wrote: On Monday, March 28, 2011, Piotr Jaroszyński wrote: I think the proper solution is to add __attribute__((unused)) to _qzz_res. What do you think? Yes. I just