public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/65392] New: Bad mangled names in Debug Mode assertions
@ 2015-03-11 18:20 redi at gcc dot gnu.org
  2015-03-11 18:21 ` [Bug libstdc++/65392] " redi at gcc dot gnu.org
  2015-05-24 12:53 ` fdumont at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2015-03-11 18:20 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 65392
           Summary: Bad mangled names in Debug Mode assertions
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org

#include <deque>

int main()
{
    std::deque<int> d;
    auto it = d.begin();
    it - 2;
}



/usr/include/c++/4.8.3/debug/safe_iterator.h:378:error: attempt to retreat 
    a past-the-end iterator 2 steps, which falls outside its valid range.

Objects involved in the operation:
iterator @ 0x0x7fff3e6b1930 {
type =
N11__gnu_debug14_Safe_iteratorINSt9__cxx199815_Deque_iteratorIiRiPiEENSt7__debug5dequeIiSaIiEEEEE
(mutable iterator);
  state = past-the-end;
  references sequence with type `NSt7__debug5dequeIiSaIiEEE' @ 0x0x7fff3e6b1930
}
Aborted (core dumped)

The types shown are not valid symbol names and cannot be demangled. They are
missing the _Z prefix.

We should not bother printing out mangled names if users can't demangle them to
get something meaningful. Ideally we should be demangling them automatically.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/65392] Bad mangled names in Debug Mode assertions
  2015-03-11 18:20 [Bug libstdc++/65392] New: Bad mangled names in Debug Mode assertions redi at gcc dot gnu.org
@ 2015-03-11 18:21 ` redi at gcc dot gnu.org
  2015-05-24 12:53 ` fdumont at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: redi at gcc dot gnu.org @ 2015-03-11 18:21 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-03-11
     Ever confirmed|0                           |1


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug libstdc++/65392] Bad mangled names in Debug Mode assertions
  2015-03-11 18:20 [Bug libstdc++/65392] New: Bad mangled names in Debug Mode assertions redi at gcc dot gnu.org
  2015-03-11 18:21 ` [Bug libstdc++/65392] " redi at gcc dot gnu.org
@ 2015-05-24 12:53 ` fdumont at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: fdumont at gcc dot gnu.org @ 2015-05-24 12:53 UTC (permalink / raw)
  To: gcc-bugs

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

François Dumont <fdumont at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |fdumont at gcc dot gnu.org
         Resolution|---                         |FIXED
           Assignee|unassigned at gcc dot gnu.org      |fdumont at gcc dot gnu.org
   Target Milestone|---                         |6.0

--- Comment #1 from François Dumont <fdumont at gcc dot gnu.org> ---
Symbols are now automatically demangle, the issue doesn't appear anymore.
>From gcc-bugs-return-487182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 24 13:56:58 2015
Return-Path: <gcc-bugs-return-487182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75906 invoked by alias); 24 May 2015 13:56:58 -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 75840 invoked by uid 48); 24 May 2015 13:56:54 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/46032] openmp inhibits loop vectorization
Date: Sun, 24 May 2015 13:56: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: 4.5.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: vries 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:
Message-ID: <bug-46032-4-ObfrC8kXKe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46032-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46032-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-05/txt/msg02022.txt.bz2
Content-length: 706

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

--- Comment #11 from vries at gcc dot gnu.org ---
The ipa-pta solution no longer works. In 4.6, we had:
...
  # USE = anything
  # CLB = anything
  GOMP_parallel_startD.1048 (main._omp_fn.0D.1472, &.omp_data_o.1D.1484, 0);
  # USE = anything
  # CLB = anything
  main._omp_fn.0D.1472 (&.omp_data_o.1D.1484);
  # USE = anything
  # CLB = anything
  GOMP_parallel_endD.1049 ();
...

On trunk, we have now:
...
  # USE = anything
  # CLB = anything
  GOMP_parallelD.1345 (main._omp_fn.0D.1844, &.omp_data_o.1D.1856, 0, 0);
...

So there's no longer a path in the call graph from main to main._omp_fn.
Perhaps a dummy body for GOMP_parallel could fix that.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-05-24 12:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-11 18:20 [Bug libstdc++/65392] New: Bad mangled names in Debug Mode assertions redi at gcc dot gnu.org
2015-03-11 18:21 ` [Bug libstdc++/65392] " redi at gcc dot gnu.org
2015-05-24 12:53 ` fdumont at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).