[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2018-02-22 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Jeffrey A. Law changed: What|Removed |Added Priority|P3 |P2 Assignee|unassigned at gcc

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2018-02-21 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #23 from Jeffrey A. Law --- Note that if we fix the abnormal handler to target the block after the setjmp rather than the setjmp itself all the problems magically disappear. That's actually a more accurate CFG and arguably the right

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2018-02-21 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Jeffrey A. Law changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2018-01-02 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #21 from Jeffrey A. Law --- No problem Eric. I'm monitoring on behalf of Florian who'd really like to see this fixed for gcc-8. Actually just noticed it still wasn't showing up in the queries. It didn't have a target milestone set

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2018-01-02 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #20 from Eric Gallager --- (In reply to Jeffrey A. Law from comment #19) > Note you lost the regression marker when this was made a duplicate of 21161. > So it's unlikely anyone would have looked at it until the next release cycle. >

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2018-01-02 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #19 from Jeffrey A. Law --- Note you lost the regression marker when this was made a duplicate of 21161. So it's unlikely anyone would have looked at it until the next release cycle. My understanding from Florian is that at least so

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-12-29 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Eric Gallager changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-12-14 Thread ygribov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Yury Gribov changed: What|Removed |Added CC||ygribov at gcc dot gnu.org --- Comment #17

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-12-14 Thread jsm28 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #16 from Joseph S. Myers --- I think the -Wclobbered warning probably needs to be reimplemented on GIMPLE, in a way that actually looks at whether it's possible for a variable to be set after the returns-twice call and before the vari

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-12-14 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Richard Biener changed: What|Removed |Added Target Milestone|--- |6.5

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-11-25 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org S

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-11-25 Thread eggert at gnu dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 --- Comment #14 from Paul Eggert --- Also please see related reports Bug 21161, Bug 48968, Bug 54561, Bug 65041, and Bug 83162. The last-listed one also is a regression, perhaps induced by the fancier optimization in recent GCC versions. I suspec

[Bug middle-end/61118] [6/7/8 Regression] Indirect call generated for pthread_cleanup_push with constant cleanup function

2017-11-21 Thread fw at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61118 Florian Weimer changed: What|Removed |Added Summary|[6/7/8 Regression] Spurious |[6/7/8 Regression] Indirect