public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/62306] [4.9/5 Regression?] Change in the comdat used for constructors Date: Tue, 02 Sep 2014 15:47:00 -0000 [thread overview] Message-ID: <bug-62306-4-xZPTfWM8Tf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62306-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62306 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- You could e.g. implement the dtors as: _Z...D0...: set some hard reg to 0 tail call some function _Z...D1...: set some hard reg to 1 tail call some function _Z...D2...: set some hard reg to 2 tail call some function and that function would just have a magic extra argument, if the same in between all levels would not use it at all, otherwise could e.g. have if (extra == 0) delete ...; at the end, etc. My memory is fuzzy on it after all the years, but as the comdat names are part of the ABI, I think the idea was to allow implementations to choose how to implement it while staying interoperable. So, if g++ 4.[569]/5 emit it in D5, I think that is how it was meant, and what should be done.
next prev parent reply other threads:[~2014-09-02 15:47 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-29 14:22 [Bug c++/62306] New: " rafael.espindola at gmail dot com 2014-08-29 20:16 ` [Bug c++/62306] " jason at gcc dot gnu.org 2014-09-01 20:58 ` rafael.espindola at gmail dot com 2014-09-02 15:33 ` rafael.espindola at gmail dot com 2014-09-02 15:47 ` jakub at gcc dot gnu.org [this message] 2014-09-02 16:24 ` rafael.espindola at gmail dot com 2014-09-02 18:04 ` rafael.espindola at gmail dot com 2014-09-03 20:45 ` jason at gcc dot gnu.org 2014-09-03 20:59 ` jakub at gcc dot gnu.org 2014-09-04 18:01 ` rafael.espindola at gmail dot com 2014-09-10 18:35 ` jason at gcc dot gnu.org 2014-09-10 18:40 ` jason at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-62306-4-xZPTfWM8Tf@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).