[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: best way to check for compiler _warnings_?
From: |
Joseph S. Myers |
Subject: |
Re: best way to check for compiler _warnings_? |
Date: |
Mon, 1 Nov 2010 17:13:32 +0000 (UTC) |
On Mon, 1 Nov 2010, Ralf Wildenhues wrote:
> > $ g++ -o /dev/null -catfood -c /tmp/s.cc ; echo $?
> > g++: unrecognized option '-catfood'
> > 0
>
> First, please complain to the compiler vendor (whoever is responsible
> for the behavior). FWIW, I can reproduce with Debian GCC 4.3.5 but not
> with upstream FSF GCC from SVN.
This was:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15303
--
Joseph S. Myers
address@hidden
- Re: best way to check for compiler _warnings_?, (continued)
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/01
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/02
- Re: best way to check for compiler _warnings_?, Peter Rosin, 2010/11/02
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/02
- Re: best way to check for compiler _warnings_?, Peter Rosin, 2010/11/02
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/02
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/02
- Re: best way to check for compiler _warnings_?, Miles Bader, 2010/11/02
- Re: best way to check for compiler _warnings_?, Ralf Wildenhues, 2010/11/03
- Re: best way to check for compiler _warnings_?, Peter Rosin, 2010/11/03
Re: best way to check for compiler _warnings_?,
Joseph S. Myers <=