On Tue, 12 May 2020, 10:15 Oleg Endo, wrote:
>
> On Tue, 2020-05-12 at 09:20 +0200, Freddie Chopin wrote:
> >
> > I actually have to build my own toolchain instead of the one provided
> > by ARM, because to really NOT use C++ exceptions, you have to recompile
> > the whole libstdc++ with `-fno-exc
On 13/05/2020 00:48, Jonathan Wakely via Gcc wrote:
On Tue, 12 May 2020 at 23:39, Jonathan Wakely wrote:
On Tue, 12 May 2020, 21:57 Freddie Chopin, wrote:
Anyway... If you have to recompile the toolchain, the problem is still
there. Most of the people (like 99,666%) will not do that for variou
On Tue, 12 May 2020 at 23:39, Jonathan Wakely wrote:
> On Tue, 12 May 2020, 21:57 Freddie Chopin, wrote:
> > Anyway... If you have to recompile the toolchain, the problem is still
> > there. Most of the people (like 99,666%) will not do that for various
> > reasons. Some don't know how, some use o
On Tue, 12 May 2020, 21:57 Freddie Chopin, wrote:
>
> On Tue, 2020-05-12 at 12:07 +0100, Jonathan Wakely wrote:
> > You're talking about C++ exceptions in general, but the problems you
> > mention seems to be issues with specific implementation properties.
>
> Possibly true, but this argument - th
On Tue, 2020-05-12 at 12:07 +0100, Jonathan Wakely wrote:
> You're talking about C++ exceptions in general, but the problems you
> mention seems to be issues with specific implementation properties.
Possibly true, but this argument - that all the problems are related to
specific implementation and
Hey.
Am 12.05.2020 um 13:29 schrieb Florian Weimer:
Would you use it if switching from -fno-exceptions to this new
approach resulted in an immediate 20% code size increase, without
actually using the new error handling feature at all? What about
10%?
I don't think that it will be that much.
W
* Moritz Strübe:
>> Would you use it if switching from -fno-exceptions to this new
>> approach resulted in an immediate 20% code size increase, without
>> actually using the new error handling feature at all? What about
>> 10%?
>
> I don't think that it will be that much.
Why? Have you simulate
Am 12.05.2020 um 11:44 schrieb Freddie Chopin:
Would you use it if switching from -fno-exceptions to this new
approach
resulted in an immediate 20% code size increase, without actually
using
the new error handling feature at all? What about 10%?
I don't think that it will be that much. I ag
On Tue, 12 May 2020 at 11:48, Freddie Chopin wrote:
> To summarize. Current C++ exceptions have very huge, mostly "one-time"
> kind, cost on the size, even if not used at all by the user, mosly due
> to std::terminate() and all the string handling code inside it, as well
> as the unwind tables.
Th
On Tue, 12 May 2020 at 09:17, Freddie Chopin wrote:
> The problem with C++ exceptions is that even in the most
> trivial of the programs and even if you don't explicitly
> use/catch/throw them, they instantly eat around 60 kB of ROM and quite
> a lot of RAM. With some hacking you can get down to ab
On Tue, 2020-05-12 at 11:16 +0200, Florian Weimer wrote:
> That can only happen if the embedded people do not bother to show up
> in
> numbers. Of course the tools will move in different directions.
True (;
> > That's why the proposal by Herb is a real surprise and I really
> > hope
> > it could
* Freddie Chopin:
> Very nice that Moritz finally mentioned it (; The world of deep
> embedded is usually forgotten by all the language committees and people
> who are in charge.
That can only happen if the embedded people do not bother to show up in
numbers. Of course the tools will move in dif
* Moritz Strübe:
> Hey.
>
> Am 11.05.2020 um 15:59 schrieb Thomas Neumann via Gcc:
>> In a way I am disagreeing with the paper, of course, in that I propose
>> to make the existing exception mechanism faster instead of inventing a
>> new exception mechanism. But what I agree on with P0709 is that
On Tue, 2020-05-12 at 09:20 +0200, Freddie Chopin wrote:
>
> I actually have to build my own toolchain instead of the one provided
> by ARM, because to really NOT use C++ exceptions, you have to recompile
> the whole libstdc++ with `-fno-exceptions -fno-rtti` (yes, I know they
> provide the "nano"
On Mon, 2020-05-11 at 17:14 +0200, Moritz Strübe wrote:
> I just wanted to point out that Herbceptions do not only fix
> performance
> issues, but also code-size problems. While anything below 4GB of RAM
> is
> considered under-powered for a PC, typical deep embedded
> environments
> have someth
Hey.
Am 11.05.2020 um 15:59 schrieb Thomas Neumann via Gcc:
In a way I am disagreeing with the paper, of course, in that I propose
to make the existing exception mechanism faster instead of inventing a
new exception mechanism. But what I agree on with P0709 is that it is
unfortunate that many pr
16 matches
Mail list logo
