public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "arthur.j.odwyer at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/113541] New: Rejects __attribute__((section)) on explicit instantiation declaration of ctor/dtor
Date: Mon, 22 Jan 2024 15:21:31 +0000	[thread overview]
Message-ID: <bug-113541-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113541

            Bug ID: 113541
           Summary: Rejects __attribute__((section)) on explicit
                    instantiation declaration of ctor/dtor
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: arthur.j.odwyer at gmail dot com
  Target Milestone: ---

// https://godbolt.org/z/34Wdj1ox8

template<class T>
struct S {
    S(int) {}
    void operator=(int) {}
    void f(int) {}
    ~S() {}
};
template __attribute__((section("TEST"))) S<int>::S(int); // error
template __attribute__((section("TEST"))) void S<int>::f(int); // OK
template __attribute__((section("TEST"))) void S<int>::operator=(int); // OK
template __attribute__((section("TEST"))) S<int>::~S(); // error

===

<source>: In instantiation of 'S<T>::S(int) [with T = int]':
<source>:9:56:   required from here
<source>:3:5: error: section of alias 'S<T>::S(int) [with T = int]' must match
section of its target
    3 |     S(int) {}
      |     ^

The problem seems to be only with the constructor and destructor, i.e., the two
kinds of functions that codegen two object-code definitions (base object xtor
and complete object xtor) for a single C++ declaration.

Somehow, giving `S` a virtual base class (`struct S : virtual B`) fixes the
problem. Then both codegenned xtors correctly wind up in the "TEST" section.

GCC 4.9.4 is happy with the code as written. The bug started happening with GCC
5.

(This was noted on Slack in June 2019, but never reported on Bugzilla AFAICT
until now: https://cpplang.slack.com/archives/C5GN4SP41/p1560800562026000 )

             reply	other threads:[~2024-01-22 15:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 15:21 arthur.j.odwyer at gmail dot com [this message]
2024-01-22 20:16 ` [Bug c++/113541] " mpolacek at gcc dot gnu.org
2024-01-23  7:46 ` rguenth 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-113541-4@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: link
Be 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).