public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: daniel@poradnik-webmastera.com
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: C++ name mangling in C
Date: Mon, 11 Aug 2014 10:45:00 -0000	[thread overview]
Message-ID: <20140811124543.Horde.pXSGtMzLIHVjX3-Xj3hoHA1@sirzooro.prohost.pl> (raw)
In-Reply-To: <CAH6eHdQxCZ0pJroHsOOt31tz-34MQPRkY9sRiGs_n+-N5AH_-Q@mail.gmail.com>


Cytowanie Jonathan Wakely <jwakely.gcc@gmail.com>:

>>> So you want GCC to behave like a C++ compiler. It can already do that.
>>>
>>> Just use C++.
>>>
>>> If you get errors, fix them.
>>
>>
>> Easier said than done. I think it will take about month of work to change
>> our code base in order to compile it using g++. We are planning to do this
>> eventually, but not now. Because of this I am looking for some temporary
>> solution to use now.
>
> It will be a lot easier to fix your code than to modify GCC to do what
> you're requesting.

I do not know GCC internals so I cannot estimate effort for such  
modification. I thought that this will not be so hard, but looks that  
is is not so easy.

BTW, I realized that there may be an easier way to do such validation  
in GCC - write information about each function prototype (found where  
function is implemented) and each function call to object files (e.g.  
as debug data or in other format), and use it to perform validation in  
linker. What do you think about this?

-- 
Regards,
Daniel

  reply	other threads:[~2014-08-11 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 19:51 daniel
2014-08-09 20:00 ` Marc Glisse
2014-08-09 20:28   ` daniel
2014-08-10  0:50 ` Jonathan Wakely
2014-08-10 19:55   ` daniel
2014-08-10 23:36     ` Jonathan Wakely
2014-08-11 10:45       ` daniel [this message]
2014-08-11 11:24         ` Jonathan Wakely
2014-08-11 12:16           ` daniel
     [not found]             ` <20140811141602.Horde.U2tZekSvXHQDnS4cFS-29A1@sirzooro.proh ost.pl>
2014-08-11 12:40               ` Fabian Cenedese
2014-08-11 11:29 ` Florian Weimer

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=20140811124543.Horde.pXSGtMzLIHVjX3-Xj3hoHA1@sirzooro.prohost.pl \
    --to=daniel@poradnik-webmastera.com \
    --cc=gcc-help@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).