> Not to mention that there is no way to enforce that on a per-call > basis in any language I know. Also, I can't think of a reason for the > front-end to decide that per function call... > > One personality definition per function should be enough...It occurs when doing LTO and inlining functions written in one language into functions written in another, thus my Ada inlined into C++ example. Mixed language programming is quite common, so it may be worth supporting this, but it's not clear. Ciao, Duncan.
On 2 December 2010 11:26, Duncan Sands <baldrick at free.fr> wrote:> It occurs when doing LTO and inlining functions written in one language > into functions written in another, thus my Ada inlined into C++ example. > Mixed language programming is quite common, so it may be worth supporting > this, but it's not clear.Good point. Still, mixing personalities in the same EH table is scary... ;) Is there any compiler that do this? -- cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm
On 02/12/10 12:53, Renato Golin wrote:> On 2 December 2010 11:26, Duncan Sands<baldrick at free.fr> wrote: >> It occurs when doing LTO and inlining functions written in one language >> into functions written in another, thus my Ada inlined into C++ example. >> Mixed language programming is quite common, so it may be worth supporting >> this, but it's not clear. > > Good point. > > Still, mixing personalities in the same EH table is scary... ;) Is > there any compiler that do this?Apparently the gcc people are working on this as part of their LTO support. Ciao, Duncan.