https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
Bernd Edlinger changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #14 from Bernd Edlinger ---
Author: edlinger
Date: Wed Aug 3 19:05:45 2016
New Revision: 239092
URL: https://gcc.gnu.org/viewcvs?rev=239092=gcc=rev
Log:
2016-08-03 Bernd Edlinger
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #12 from Bernd Edlinger ---
Author: edlinger
Date: Thu Jul 21 19:06:02 2016
New Revision: 238605
URL: https://gcc.gnu.org/viewcvs?rev=238605=gcc=rev
Log:
016-07-21 Bernd Edlinger
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #13 from Bernd Edlinger ---
Author: edlinger
Date: Thu Jul 21 19:11:26 2016
New Revision: 238606
URL: https://gcc.gnu.org/viewcvs?rev=238606=gcc=rev
Log:
016-07-21 Bernd Edlinger
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #11 from Bernd Edlinger ---
(In reply to Jeffrey A. Law from comment #10)
> No opinion on the "x" prefix. I think that was already in place when that
> code was updated to support qsetjmp and savectx in the early 90s. I've
> never
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #10 from Jeffrey A. Law ---
No opinion on the "x" prefix. I think that was already in place when that code
was updated to support qsetjmp and savectx in the early 90s. I've never seen
the "x" versions in practice.
ANd yes, you're
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #9 from Bernd Edlinger ---
(In reply to Jeffrey A. Law from comment #8)
> Light searching doesn't find anything useful for setjmp_syscall.
>
> savectx however still shows up in a variety of solaris searches. In fact,
> you can find
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
Jeffrey A. Law changed:
What|Removed |Added
CC||law at redhat dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #7 from Bernd Edlinger ---
Created attachment 38915
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38915=edit
possible patch
This is an attempt of a fix.
Not really perfect, but should be at least safe.
Only ECF_RETURN_TWICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #6 from Bernd Edlinger ---
(In reply to Jakub Jelinek from comment #5)
> Perhaps ECF_MAY_BE_ALLOCA too? But ECF_NORETURN and ECF_LEAF are not
> conservative, sure.
Yes. That's right.
alloca can not return null.
See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #4 from Bernd Edlinger ---
And, what is "qsetjmp" ?
Also "setjmp_syscall", "savectx" are also completely new to me.
And why is the prefix "__x" discarded?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
13 matches
Mail list logo