[Bug fortran/67460] New: [5/6 Regression] Spurious: f951: all warnings being treated as errors

[Bug fortran/67460] New: [5/6 Regression] Spurious: f951: all warnings being treated as errors

[Joost.VandeVondele at mat dot ethz.ch]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

            Bug ID: 67460
           Summary: [5/6 Regression] Spurious: f951: all warnings being
                    treated as errors
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Joost.VandeVondele at mat dot ethz.ch
  Target Milestone: ---

The testcase below leads to spurious output at compile time, even though no
warning (or error) is emitted. This started with the 5. release, 4.9 is fine.
In a large build this can trigger many times, but it does not always trigger.

> gfortran  -c -std=f2003 -Werror bug.f90
f951: all warnings being treated as errors

> cat bug.f90
MODULE btree_i8_k_sp2d_v
  TYPE btree_node
     INTEGER id
     TYPE(btree_node_p), DIMENSION(:), POINTER :: subtrees
     TYPE(btree_node), POINTER :: parent
  END TYPE btree_node
  TYPE btree_node_p
     TYPE(btree_node), POINTER :: node
  END TYPE btree_node_p
CONTAINS
  RECURSIVE SUBROUTINE btree_verify_node (tree, node, level, nids, lastv,&
               count, num_nodes, max_leaf_level, min_leaf_level, printing)
    TYPE(btree_node), INTENT(IN)             :: node
    INTEGER                                  :: branch
    IF (ASSOCIATED (node%subtrees(branch)%node)) THEN
       IF (node%subtrees(branch)%node%parent%id .NE. node%id) THEN
          WRITE(*,*)'foo'
       ENDIF
    ENDIF
  END SUBROUTINE btree_verify_node
END MODULE btree_i8_k_sp2d_v

[Bug fortran/67460] [5/6 Regression] Spurious: f951: all warnings being treated as errors

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-09-05
                 CC|                            |manu at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
No error with revision r218658 (2014-12-12), error with r218716 (2014-12-14),
likely r218694.

[Bug fortran/67460] [5/6 Regression] Spurious: f951: all warnings being treated as errors

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

--- Comment #2 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Again a problem caused by buffering. Some warnings converted into error may get
buffered and then discarded but that doesn't reset ->some_warnings_are_errors.
However, we probably do not need this variable at all, since we now count
explicitly how many warnings were converted into errors and this number is kept
up to date for buffered diagnostics. I think this patch should fix it, but I
have not tested it yet:

Index: diagnostic.c
===================================================================
--- diagnostic.c        (revision 227395)
+++ diagnostic.c        (working copy)
@@ -135,11 +135,10 @@ diagnostic_initialize (diagnostic_contex
      much more elaborated pretty-printer if they wish.  */
   context->printer = XNEW (pretty_printer);
   new (context->printer) pretty_printer ();

   memset (context->diagnostic_count, 0, sizeof context->diagnostic_count);
-  context->some_warnings_are_errors = false;
   context->warning_as_error_requested = false;
   context->n_opts = n_opts;
   context->classify_diagnostic = XNEWVEC (diagnostic_t, n_opts);
   for (i = 0; i < n_opts; i++)
     context->classify_diagnostic[i] = DK_UNSPECIFIED;
@@ -202,11 +201,11 @@ diagnostic_color_init (diagnostic_contex

 void
 diagnostic_finish (diagnostic_context *context)
 {
   /* Some of the errors may actually have been warnings.  */
-  if (context->some_warnings_are_errors)
+  if (diagnostic_kind_count (context, DK_WERROR))
     {
       /* -Werror was given.  */
       if (context->warning_as_error_requested)
        pp_verbatim (context->printer,
                     _("%s: all warnings being treated as errors"),
@@ -859,13 +858,10 @@ diagnostic_report_diagnostic (diagnostic
         warnings for ranges of source code.  */
       if (diagnostic->kind == DK_IGNORED)
        return false;
     }

-  if (orig_diag_kind == DK_WARNING && diagnostic->kind == DK_ERROR)
-    context->some_warnings_are_errors = true;
-
   context->lock++;

   if (diagnostic->kind == DK_ICE || diagnostic->kind == DK_ICE_NOBT)
     {
 #ifndef ENABLE_CHECKING
Index: diagnostic.h
===================================================================
--- diagnostic.h        (revision 227395)
+++ diagnostic.h        (working copy)
@@ -64,14 +64,10 @@ struct diagnostic_context
   pretty_printer *printer;

   /* The number of times we have issued diagnostics.  */
   int diagnostic_count[DK_LAST_DIAGNOSTIC_KIND];

-  /* True if we should display the "warnings are being tread as error"
-     message, usually displayed once per compiler run.  */
-  bool some_warnings_are_errors;
-
   /* True if it has been requested that warnings be treated as errors.  */
   bool warning_as_error_requested;

   /* The number of option indexes that can be passed to warning() et
      al.  */
>From gcc-bugs-return-496446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Sep 05 18:17:38 2015
Return-Path: <gcc-bugs-return-496446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32799 invoked by alias); 5 Sep 2015 18:17:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32767 invoked by uid 48); 5 Sep 2015 18:17:34 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66189] Block loops for inline matmul
Date: Sat, 05 Sep 2015 18:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-66189-4-MwjtLff66W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66189-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66189-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00424.txt.bz2
Content-length: 600

https://gcc.gnu.org/bugzilla/show_bug.cgi?idf189

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-09-05
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
IMO the matmul inlining should be restricted to small matrices, thus I am not
convinced that this worth the work.

[Bug fortran/67460] [5/6 Regression] Spurious: f951: all warnings being treated as errors

[Joost.VandeVondele at mat dot ethz.ch]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

--- Comment #3 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
(In reply to Manuel López-Ibáñez from comment #2)
> Again a problem caused by buffering. Some warnings converted into error may
> get buffered and then discarded but that doesn't reset
> ->some_warnings_are_errors. However, we probably do not need this variable
> at all, since we now count explicitly how many warnings were converted into
> errors and this number is kept up to date for buffered diagnostics. I think
> this patch should fix it, but I have not tested it yet:

yes, fixes the testcase.
>From gcc-bugs-return-496448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Sep 05 19:02:15 2015
Return-Path: <gcc-bugs-return-496448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114581 invoked by alias); 5 Sep 2015 19:02:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114514 invoked by uid 48); 5 Sep 2015 19:02:11 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/66236] [6 Regression] FAIL: gcc.c-torture/execute/pr42691.c on alpha-linux-gnu
Date: Sat, 05 Sep 2015 19:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: thopre01 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-66236-4-UcU8sX7zoh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66236-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66236-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00426.txt.bz2
Content-length: 865

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66236

Bernd Edlinger <bernd.edlinger at hotmail dot de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernd.edlinger at hotmail dot de

--- Comment #5 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to Uroš Bizjak from comment #4)
> (In reply to Thomas Preud'homme from comment #3)
> > Alternatively, you can try the patch proposed at [1] and see if it fixes the
> > issue you're facing since it seems to be the same one.
> > 
> > [1] https://gcc.gnu.org/ml/gcc-patches/2015-05/msg01901.html
> 
> Thomas,
> 
> yes the referred patch also fixes this issue.
> 
> Thanks!

that was committed already.  Thus this one should be fixed too?
>From gcc-bugs-return-496449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Sep 05 19:05:46 2015
Return-Path: <gcc-bugs-return-496449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128337 invoked by alias); 5 Sep 2015 19:05:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128285 invoked by uid 48); 5 Sep 2015 19:05:43 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/66236] [6 Regression] FAIL: gcc.c-torture/execute/pr42691.c on alpha-linux-gnu
Date: Sat, 05 Sep 2015 19:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: thopre01 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-66236-4-tPHjyA9r75@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66236-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66236-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00427.txt.bz2
Content-length: 556

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66236

Uroš Bizjak <ubizjak at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Bernd Edlinger from comment #5)

> that was committed already.  Thus this one should be fixed too?

Yes, this was fixed.
>From gcc-bugs-return-496450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Sep 05 19:48:52 2015
Return-Path: <gcc-bugs-return-496450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78226 invoked by alias); 5 Sep 2015 19:48:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78184 invoked by uid 48); 5 Sep 2015 19:48:48 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/67464] New: wrong code at -O3 on x86_64-linux-gnu
Date: Sat, 05 Sep 2015 19:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-67464-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg00428.txt.bz2
Content-length: 1481

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg464

            Bug ID: 67464
           Summary: wrong code at -O3 on x86_64-linux-gnu
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: su at cs dot ucdavis.edu
  Target Milestone: ---

The current gcc trunk miscompiles the following code on x86_64-linux-gnu at -O3
in both 32-bit and 64-bit modes.

This is a regression from 5.2.x.


$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/usr/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/6.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --prefix=/usr/local/gcc-trunk
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 6.0.0 20150905 (experimental) [trunk revision 227508] (GCC)
$
$ gcc-trunk -O2 small.c; ./a.out
01
$ gcc-5.2 -O3 small.c; ./a.out
01
$
$ gcc-trunk -O3 small.c
$ ./a.out
00
$


---------------------------------


int printf (const char *, ...);

int a = 1, b, c, d, e, f, g;

void
fn1 ()
{
  c = b;
  for (; d; d--)
    ;
  for (f = 0; f < 1; f++)
    for (e = 0; e < 1; e++)
      c = 0;
}

int
main ()
{
  int h = a;
  b = h = g < 1 ? a : a < 0;
  for (a = 0; a < 1; a++)
    fn1 ();
  printf ("0");
  printf ("%d\n", b);  // b should be 1, not 0
  return 0;
}

[Bug fortran/67460] [5/6 Regression] Spurious: f951: all warnings being treated as errors

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
patch submitted: https://gcc.gnu.org/ml/gcc-patches/2015-09/msg00894.html
>From gcc-bugs-return-497129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 14 00:07:12 2015
Return-Path: <gcc-bugs-return-497129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29062 invoked by alias); 14 Sep 2015 00:07:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28998 invoked by uid 48); 14 Sep 2015 00:07:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67557] Calling copy constructor of base class in constructor of derived class produces crashing code
Date: Mon, 14 Sep 2015 00:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on resolution everconfirmed
Message-ID: <bug-67557-4-hnR9G4b5CH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67557-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67557-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01107.txt.bz2
Content-length: 1471

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67557

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
   Last reconfirmed|                            |2015-09-14
         Resolution|INVALID                     |---
     Ever confirmed|0                           |1

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
There's nothing invalid about the program, no member function is called on the
object being constructed (except the constructor, but obviously you have to
call a constructor before the object is constructed!)

After x has been constructed its string member has an invalid pointer:

(gdb) p/r  x.tag_
$1 = {static npos = 18446744073709551615, _M_dataplus = {<std::allocator<char>>
= {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>},
_M_p = 0x7fffffffd380 ""}, _M_string_length = 0, {
    _M_local_buf = "\000\001\241Y9\000\000\000Щ\304\367\377\177\000",
_M_allocated_capacity = 246316859648}}
(gdb) p x.tag_._M_local_buf + 0
$2 = 0x7fffffffd3f0 ""

(gdb) p x.tag_._M_dataplus._M_p
$3 = (std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >::pointer) 0x7fffffffd380 ""


N.B. 0x7fffffffd380 != 0x7fffffffd3f0

The code works correctly with -fno-elide-constructors
>From gcc-bugs-return-497130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 14 00:36:46 2015
Return-Path: <gcc-bugs-return-497130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126475 invoked by alias); 14 Sep 2015 00:36:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126417 invoked by uid 48); 14 Sep 2015 00:36:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67557] Calling copy constructor of base class in constructor of derived class produces crashing code
Date: Mon, 14 Sep 2015 00:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.1.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-67557-4-keMYPXVHAU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67557-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67557-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01108.txt.bz2
Content-length: 1810

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg557

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |wrong-code

--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
namespace std
{
struct string
{
  typedef unsigned long size_type;
  const char* _M_p;
  char        _M_local_buf[1];

  string(const char* s) : _M_p(_M_local_buf)
  {
    __builtin_printf("%p constructed\n", this);
  }

  string(const string& s) : _M_p(_M_local_buf)
  {
    __builtin_printf("%p copied from %p\n", this, &s);
  }

  ~string()
  {
    __builtin_printf("%p destroyed\n", this);
    if (_M_p != _M_local_buf)
      __builtin_abort();
  }
};
}

struct StartTag
{
        explicit StartTag(std::string const & tag) : tag_(tag),
keepempty_(false) {}
        std::string tag_;
        bool keepempty_;
};

StartTag fontToStartTag() { return StartTag(""); }

struct FontTag : public StartTag
{
        FontTag() : StartTag(fontToStartTag()) {}
};

int main()
{
        FontTag x;
        __builtin_printf("%p x.tag_ in main()\n", &x.tag_);
        return 0;
}


This prints:

0x7ffdd31bbb60 constructed
0x7ffdd31bbb90 copied from 0x7ffdd31bbb60
0x7ffdd31bbb60 destroyed
0x7ffdd31bbbe0 x.tag_ in main()
0x7ffdd31bbbe0 destroyed
Aborted (core dumped)

Note that the 'this' pointer in the copy constructor is 0x7fffde6c4d20, which
is not the address of x.tag_ and not the address in the destructor.

The string copy constructor sets its _M_p member to point to this->_M_local_buf
using the incorrect value of 'this' and then in the destructor sees _M_p !_M_local_buf (which in the real std::string tries to delete[] _M_p which
crashes).

[Bug fortran/67460] [5/6 Regression] Spurious: f951: all warnings being treated as errors

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

--- Comment #5 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Author: manu
Date: Mon Sep 14 19:27:50 2015
New Revision: 227760

URL: https://gcc.gnu.org/viewcvs?rev=227760&root=gcc&view=rev
Log:
The flag diagnostic_context::some_warnings_are_errors controls whether
to give the message "all warnings being treated as errors". However, when
warnings are buffered and then discarded, this flag is not reset. It turns
out we do not need this flag at all, since we already count explicitly how
many warnings were converted into errors, and this number is kept up to
date for the buffered diagnostics used by Fortran.

gcc/ChangeLog:

2015-09-14  Manuel López-Ibáñez  <manu@gcc.gnu.org>

        PR fortran/67460
        * diagnostic.c (diagnostic_initialize): Do not set
        some_warnings_are_errors.
        (diagnostic_finish): Use DK_WERROR count instead.
        (diagnostic_report_diagnostic): Do not set
        some_warnings_are_errors.
        * diagnostic.h (struct diagnostic_context): Remove
        some_warnings_are_errors.

gcc/testsuite/ChangeLog:

2015-09-14  Manuel López-Ibáñez  <manu@gcc.gnu.org>

        PR fortran/67460
        * gfortran.dg/pr67460.f90: New test.



Added:
    trunk/gcc/testsuite/gfortran.dg/pr67460.f90
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/diagnostic.c
    trunk/gcc/diagnostic.h
    trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-497210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 14 19:31:08 2015
Return-Path: <gcc-bugs-return-497210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121328 invoked by alias); 14 Sep 2015 19:31:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121295 invoked by uid 48); 14 Sep 2015 19:31:05 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67460] [5 Regression] Spurious: f951: all warnings being treated as errors
Date: Mon, 14 Sep 2015 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-67460-4-QHwkeGGDiS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67460-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67460-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01188.txt.bz2
Content-length: 732

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |6.0
   Target Milestone|---                         |5.2
            Summary|[5/6 Regression] Spurious:  |[5 Regression] Spurious:
                   |f951: all warnings being    |f951: all warnings being
                   |treated as errors           |treated as errors
      Known to fail|6.0                         |

--- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
Fixed in GCC 6.
>From gcc-bugs-return-497211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 14 19:31:16 2015
Return-Path: <gcc-bugs-return-497211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122041 invoked by alias); 14 Sep 2015 19:31:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121809 invoked by uid 48); 14 Sep 2015 19:31:12 -0000
From: "Casey at Carter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67579] New: [concepts] Memoization for constraint expressions
Date: Mon, 14 Sep 2015 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: Casey at Carter dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-67579-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-09/txt/msg01189.txt.bz2
Content-length: 1533

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg579

            Bug ID: 67579
           Summary: [concepts] Memoization for constraint expressions
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: Casey at Carter dot net
  Target Milestone: ---

While implementing the Ranges TS I've found that the implementation of concepts
in GCC scales very poorly to larger and more complex systems. I've been able to
achieve 1-2 order of magnitude improvements in compile time and memory usage by
hand coding memoization for some concepts with constexpr variable templates.
E.g., replacing

  template </* parameters */>
  concept bool Foo = // requirements

with

  template </* parameters */>
  constexpr bool Foo_ = false;
  template </* parameters */>
    requires // requirements
  constexpr bool Foo_</* parameter names */> = true;

  template </* parameters */>
  concept bool Foo = Foo_</* parameter names */>;

which is fine when Foo need not participate in subsumption relationships. If
Foo *does* need to participate in subsumption relationships then performing
this transformation by hand is not possible since it hides the relationship
between Foo and "requirements" from the compiler's view.

If concepts & constraint expressions are to be generally applicable the
implementation must provide some means of reducing the cost of repeated
evaluation.

[Bug fortran/67460] [5 Regression] Spurious: f951: all warnings being treated as errors

[pault at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pault at gcc dot gnu.org

--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #6)
> Fixed in GCC 6.

Hi Manuel,

Are you going to fix 5 branch as well? If not, would you like me to do the
honours for you?

Cheers

Paul
>From gcc-bugs-return-500047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 20 11:43:08 2015
Return-Path: <gcc-bugs-return-500047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34180 invoked by alias); 20 Oct 2015 11:43:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34141 invoked by uid 48); 20 Oct 2015 11:43:04 -0000
From: "daniel.gutson at tallertechnologies dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67064] Register asm variable broken
Date: Tue, 20 Oct 2015 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daniel.gutson at tallertechnologies dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: daniel.gutson at tallertechnologies dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67064-4-Q1Tcie53YK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67064-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67064-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg01602.txt.bz2
Content-length: 205

https://gcc.gnu.org/bugzilla/show_bug.cgi?idg064

--- Comment #30 from Daniel Gutson <daniel.gutson at tallertechnologies dot com> ---
May I ask what's wrong with Andres Tiraboschi's solution approach?

[Bug fortran/67460] [5 Regression] Spurious: f951: all warnings being treated as errors

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67460

--- Comment #8 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Paul Thomas from comment #7)
> Are you going to fix 5 branch as well? If not, would you like me to do the
> honours for you?

Please do it. I have no free time to spend on GCC these days. I also changed
universities so I would need a new copyright assignment and I'm not really
looking forward to fighting that fight yet again.
>From gcc-bugs-return-500052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Oct 20 12:35:21 2015
Return-Path: <gcc-bugs-return-500052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41024 invoked by alias); 20 Oct 2015 12:35:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37430 invoked by uid 48); 20 Oct 2015 12:35:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/68017] ICE on valid code at -O3 with -g enabled on x86_64-linux-gnu: cannot update SSA form
Date: Tue, 20 Oct 2015 12:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone short_desc
Message-ID: <bug-68017-4-If7W1erp2L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68017-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68017-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg01607.txt.bz2
Content-length: 732

https://gcc.gnu.org/bugzilla/show_bug.cgi?idh017

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |6.0
   Target Milestone|6.0                         |5.3
            Summary|[6 Regression] ICE on valid |ICE on valid code at -O3
                   |code at -O3 with -g enabled |with -g enabled on
                   |on x86_64-linux-gnu: cannot |x86_64-linux-gnu: cannot
                   |update SSA form             |update SSA form

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar, queued for 5.3