> Hmm, I am still not following. By EH-neutral you mean function compiled > with -fno-exceptions so it has no unwind info at all or one that has unwind > info but does not do anything with EH?
OK, I see what you mean now. So, even if lto_init_eh is never invoked and thus never sets flag_exceptions for the partition, you would record whether the flag was saved in the optimization node of at least one function, right? But this would require to compile C code with -fexceptions if it's included in an EH-enabled LTO link, whereas you didn't need do it previously (of course this is all masked on x86 because -funwind-tables is always enabled). On the other hand, this is required for a normal link too. I guess that would be more consistent with what happens with -fdwarf2-cfi-asm. -- Eric Botcazou
