[Bug c++/57378] gnu multiversioning gives assembler error: foo.resolver is already defined

2024-04-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57378 --- Comment #5 from Andrew Pinski --- Note with checking enabled we get an ICE: :23:17: error: Two symbols with same comdat_group are not linked by the same_comdat_group list. 23 | { return foo(); } | ^

[Bug c++/57378] gnu multiversioning gives assembler error: foo.resolver is already defined

2019-05-02 Thread nheart at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57378 Nikolay Bogoychev changed: What|Removed |Added CC||nheart at gmail dot com --- Comment

[Bug c++/57378] gnu multiversioning gives assembler error: foo.resolver is already defined

2013-05-23 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57378 Richard Biener rguenth at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug c++/57378] gnu multiversioning gives assembler error: foo.resolver is already defined

2013-05-23 Thread tmsriram at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57378 Sriraman Tallam tmsriram at google dot com changed: What|Removed |Added CC||davidxl at

[Bug c++/57378] gnu multiversioning gives assembler error: foo.resolver is already defined

2013-05-23 Thread davidxl at google dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57378 --- Comment #3 from davidxl at google dot com --- Can the resolver node be updated? or a new dispatcher/resolver is created? The user code looks fine to me, which exposes the implementation limitation. David (In reply to Sriraman Tallam from