LPC and other questions ?
Hello and good morning, Recently I had the privilege of stumbling upon a few of the videos on youtube. I really found them helpful, and learned quite a bit. I will say I probably have to watch them a few more times to even begin to have a level of understanding that everyone had years ago Anyway, there are a few things I noticed and wanted to reach out. >From the list of sponsors, I thought the company that I work with would be one >as well, but more than likely there are no one aware.. I am not in any >position to make any decisions on that level at all, but I don't think it >would hurt if you could describe to me the process and I could forward that >information to someone.. somewhere.. I'm not sure how all of these things would work at the moment.. Anyway, I was also wondering about rust ? I have not used it yet, usually I use gcc/gcc-c++/gcc-gfortran for most cases. Is there another webpage I could check out also? There are also other issues that I am starting to notice and am having trouble verifying a few things, and it might or might not be good to be verified.. I don't know.. Maybe we can discuss this later sometime. Thanks for your time, Have a good day -Joseph
Are _Unwind_Find_FDE et al. part of the public ABI?
_Unwind_Find_FDE is exported as a public symbol on GNU/Linux, with a default symbol version. But it's not part of the install header, and its struct types are not namespace-clean for C++, potentially leading to ODR violations. What should we do with _Unwind_Find_FDE and similar exported functions that require types which are not currently defined in ? Thanks, Florian
Re: Are _Unwind_Find_FDE et al. part of the public ABI?
On Okt 25 2021, Florian Weimer via Gcc wrote: > What should we do with _Unwind_Find_FDE and similar exported functions > that require types which are not currently defined in ? Aren't they legacy only? Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: Are _Unwind_Find_FDE et al. part of the public ABI?
* Andreas Schwab: > On Okt 25 2021, Florian Weimer via Gcc wrote: > >> What should we do with _Unwind_Find_FDE and similar exported functions >> that require types which are not currently defined in ? > > Aren't they legacy only? Sorry, I don't understand. _Unwind_Find_FDE is a key part of the unwinder used for exception handling. It's definitely still in use. But it looks like an internal implementation detail that was exported by mistake. Thanks, Florian
Re: Are _Unwind_Find_FDE et al. part of the public ABI?
On Okt 25 2021, Florian Weimer wrote: > Sorry, I don't understand. _Unwind_Find_FDE is a key part of the > unwinder used for exception handling. It's definitely still in use. Not on new platforms. See libc_cv_gcc_unwind_find_fde. > But it looks like an internal implementation detail that was exported by > mistake. What I said. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
Re: Are _Unwind_Find_FDE et al. part of the public ABI?
Sorry, I thought this was the libc list... :-) Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
[no subject]
I am pleased to announce that the GCC Steering Committee has appointed Maciej W. Rozycki as maintainer of the Vax backend in GCC. Maciej, please update your listing in the MAINTAINERS file. Good luck! --joel
