From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14312 invoked by alias); 24 Nov 2005 10:36:03 -0000 Received: (qmail 14302 invoked by uid 48); 24 Nov 2005 10:36:01 -0000 Date: Thu, 24 Nov 2005 10:36:00 -0000 Subject: [Bug c++/25015] New: [gomp] Function names cannot be demangled due to ".omp_fn" suffix X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "reichelt at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2005-11/txt/msg03344.txt.bz2 List-Id: Compiling the following code snippet with "g++ -fopenmp -O -Wall" I get a hosed error message: ============================ int i; void foo() { #pragma omp parallel { int j; i = j; } } ============================ bug.cc: In function 'void _Z3foov.omp_fn.0(void*)': bug.cc:8: warning: 'j' is used uninitialized in this function Because of the ".omp_fn.0" at the end of the function name the demangler cannot process it. Jakub, this is because of your patch http://gcc.gnu.org/ml/gcc-patches/2005-10/msg01644.html Should we regard the ".omp_fn.0" suffix as an extension to the name mangling scheme and teach the demangler how to handle those things? This problem will probably also come up with debuggers etc. -- Summary: [gomp] Function names cannot be demangled due to ".omp_fn" suffix Product: gcc Version: unknown Status: UNCONFIRMED Keywords: diagnostic, monitored, openmp Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25015