[Bug c++/80792] worse code generated compared to clang when using std::tuple

2018-08-23 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80792 Marc Glisse changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/80792] worse code generated compared to clang when using std::tuple

2017-11-24 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80792 --- Comment #3 from Marc Glisse --- It seems that clang have fixed their ABI to generate code similar to gcc. Any objection to closing this?

[Bug c++/80792] worse code generated compared to clang when using std::tuple

2017-05-17 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80792 --- Comment #2 from Jonathan Wakely --- https://bugs.llvm.org/show_bug.cgi?id=19668

[Bug c++/80792] worse code generated compared to clang when using std::tuple

2017-05-16 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80792 --- Comment #1 from Marc Glisse --- There seems to be an ABI issue here, clang returns the tuple in a register, but (according to PR 71301) it shouldn't, with current libstdc++ code (and g++ doesn't).