Snapshot gcc-5-20160614 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20160614/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
On 14/06/16 10:32, Florian Weimer wrote:
A long time ago, GCC decided that warn_unused_result warnings should *not* be
silenced by casting to void, as in:
(void) write (STDOUT_FILENO, message, strlen (message));
Apparently, programmers have figured out to use this idiom as a replacement:
On Fri, Jun 10, 2016 at 11:31:33 +0200, Jakub Jelinek wrote:
> On Fri, Jun 10, 2016 at 09:39:02AM +0200, Thomas Schwinge wrote:
> > But I'm actually confused as to seeing libgomp.so in that list -- given
> > the conflict of which compiler installations' libgomp.so "wins", I wonder
> > how it can be
On 14/06/16 10:32, Florian Weimer wrote:
A long time ago, GCC decided that warn_unused_result warnings should
*not* be silenced by casting to void, as in:
(void) write (STDOUT_FILENO, message, strlen (message));
Apparently, programmers have figured out to use this idiom as a replacement:
A long time ago, GCC decided that warn_unused_result warnings should
*not* be silenced by casting to void, as in:
(void) write (STDOUT_FILENO, message, strlen (message));
Apparently, programmers have figured out to use this idiom as a replacement:
if (write (STDOUT_FILENO, message, strlen
