public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/25015] [gomp] Function names cannot be demangled due to ".omp_fn" suffix
Date: Fri, 25 Nov 2005 22:38:00 -0000	[thread overview]
Message-ID: <20051125223809.6027.qmail@sourceware.org> (raw)
In-Reply-To: <bug-25015-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rth at gcc dot gnu dot org  2005-11-25 22:38 -------
No, this isn't a failure of the demangler.  Nor do ever expect these 
functions to ever be demangled.  That they contain the original function
name at all is merely an aid to us the compiler developer.

I don't see that this is any better or worse, from the user's perspective,
than just "__omp_fn.N", which is what we had before the patch.

Unless you can come up with some convincing user usage scenario, I'm not
going to address this problem at all.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25015


  parent reply	other threads:[~2005-11-25 22:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 10:36 [Bug c++/25015] New: " reichelt at gcc dot gnu dot org
2005-11-25 20:31 ` [Bug c++/25015] " pinskia at gcc dot gnu dot org
2005-11-25 22:38 ` rth at gcc dot gnu dot org [this message]
2006-02-26 19:16 ` pinskia at gcc dot gnu dot org
2006-03-27 16:29 ` jakub at gcc dot gnu dot org
     [not found] <bug-25015-4@http.gcc.gnu.org/bugzilla/>
2011-09-27  8:54 ` paolo.carlini at oracle dot com
2013-12-16  1:04 ` d.g.gorbachev at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051125223809.6027.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).