This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH: Factor __aeabi_atexit into its own object file

From: Paolo Carlini <pcarlini at suse dot de>
To: Mark Mitchell <mark at codesourcery dot com>
Cc: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Tue, 08 May 2007 10:40:29 +0200
Subject: Re: PATCH: Factor __aeabi_atexit into its own object file
References: <200705040350.l443oAb6016685@sparrowhawk.codesourcery.com> <463BCC94.30608@suse.de> <463FF874.1050409@codesourcery.com>

Mark Mitchell wrote:

How about this patch, as a solution? (To replace the quick hack I checked in when you reported this to me.)

Ah, if I understand it correctly (i'm not very familiar with attribute((nothrow)), just browsed the docs about it), seems a very good idea to me. But now I suspect such attribute could be potentially usefully added to many more functions? Could you clarify?

Thanks,
Paolo.

Follow-Ups:
- Re: PATCH: Factor __aeabi_atexit into its own object file
  - From: Mark Mitchell

References:
- PATCH: Factor __aeabi_atexit into its own object file
  - From: Mark Mitchell
- Re: PATCH: Factor __aeabi_atexit into its own object file
  - From: Paolo Carlini
- Re: PATCH: Factor __aeabi_atexit into its own object file
  - From: Mark Mitchell

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]