Snapshot gcc-8-20170430 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20170430/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
Hello!
A code that I wrote was warning-free in GCC 4.9, GCC 5 and GCC 6. It
was also warning-free with some older GCC 7 experimental snapshots (for
example 7-20170409). But in the most recent snapshot (including the
first RC), it started to produce a warning about aliasing. The code
basically boil
On Sun, Apr 30, 2017 at 07:49:45PM +0200, Gerald Pfeifer wrote:
> On Tue, 25 Apr 2017, Jakub Jelinek wrote:
> > Committed to trunk, 7.x will need to wait until 7.1 is released,
> > the rc1 is already in the works and this isn't anything new, I
> > see the same thing already in GCC 4.0.
>
> Thank
On Sun, Apr 30, 2017 at 7:23 PM, Martin Sebor wrote:
> The warning is triggered by the fscanf function being decorated
> with attribute warn_unused_result in the header. The
> header is part of libc, not GCC, so the appropriate place to
> raise a concern with it would on the libc mailing list (s
On Tue, 25 Apr 2017, Jakub Jelinek wrote:
> Committed to trunk, 7.x will need to wait until 7.1 is released,
> the rc1 is already in the works and this isn't anything new, I
> see the same thing already in GCC 4.0.
Thanks, Jakub! Are you planning to apply this to GCC 7 after the
release of 7.1?
On 04/29/2017 11:50 AM, Sebastian Noack wrote:
Hi everybody,
If you use -D_FORTIFY_SOURCE=2 (or 1), some additionally checks, both,
at compile- and run-time, supposed to catch buffer overflows, are
performed. Debian (and some other distributions) use this option by
default, when packaging softwa
