Re: Trouble with alloca.h
Eli Zaretskii <eliz-mXXj517/[email protected]>
| Newsgroups | gmane.comp.gnu.mingw.user |
|---|---|
| Message-ID | <[email protected]> |
> From: Keith Marshall <[email protected]> > Date: Fri, 8 Mar 2019 18:14:28 +0000 > > > GCC never inlines a function that calls alloca() or __builtin_alloca(). > > The reason is that if you call this function in a loop, then without > > inlining it will consume a bounded amount of stack whereas with inlining > > it might cause a stack overflow. > > > > The mingw people have declared their new alloca() function as "always > > inline", and GCC is decent enough to point us to the dilemma that it > > cannot resolve. > > No disrespect of Bruno intended, but, at least with GCC-8.2, I can see > no evidence whatsoever to support this claim; quite the contrary, in > fact! That was also my conclusion. Please help me to revive that discussion, as it seems to have stalled, and my recent ping didn't help. _______________________________________________ MinGW-Users mailing list [email protected] This list observes the Etiquette found at http://www.mingw.org/Mailing_Lists. We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. _______________________________________________ You may change your MinGW Account Options or unsubscribe at: https://lists.osdn.me/mailman/listinfo/mingw-users Also: mailto:[email protected]?subject=unsubscribe