Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: C++ forcing unnecessary changes to C?
Date: Tue, 22 Nov 2016 08:58:40 -0800
Organization: None to speak of
Lines: 39
Message-ID: <ln8tsbe9j3.fsf@kst-u.example.com>
References: <o0mseq$e7o$1@dont-email.me> <o115oq$84f$2@dont-email.me> <o118p6$j9q$1@dont-email.me> <o11if4$kqh$2@dont-email.me> <o11lu5$2t4$1@dont-email.me> <o11mib$57i$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: mx02.eternal-september.org; posting-host="0025a28d334b2c37a4ed25218779b166"; logging-data="22533"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/NPLVs35AnsLtWRWBVIs86"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:zRFeIlGgY6JQ9VLbTuGU6c4arXk= sha1:Qs+KvW+aYHGJS6slZGgc/xsVOjM=
Xref: csiph.com comp.lang.c:97289

BartC <bc@freeuk.com> writes:
> On 22/11/2016 14:50, David Brown wrote:
>> On 22/11/16 14:51, jacobnavia wrote:
>>> Le 22/11/2016 à 12:05, David Brown a écrit :
>>>> So gcc certainly does not generate exception tables for C compilation.
>>>
>>> This is FALSE. See the thread I started "Negative effects of c++ in C".
>>> For your convenience here is a msg:
>>>
>>> No, I am talking about gcc. For instance I have a program called "asm",
>>> an assembler, featuring
>>>
>>> jacob@linux-mint ~/lcc/asm/asm4 $ ls -l asm
>
> (Thanks. I've been wondering how to get 'ls' to give me a file size in 
> bytes!)

`man ls`?  `ls --help`?

g>>> ALL the sources are in straight C and I have to pay 103,506 c++ taxes!
>>>
>>> For NOTHING since C has no throws!
>>
>> A little research shows that this is a /requirement/ of the x86-64 ABI.
>
> That sounds unlikely. After all Jacob produces his own compiler for 
> x64-ABI; you'd think he would know if that was the case!

The ABI document is http://www.x86-64.org/documentation/abi.pdf .
(The web site seems to be down at the moment.)  Sections 3.3.1,
Exception Interface, and 6.3, Unwinding Through Assembler Code,
seem relevant.  I haven't read it closely enough to know just what
it requires.  Perhaps David can provide more details.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"