<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/133246>133246</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            differences between GCC and LLVM with __attribute__((constructor)) __attribute__((destructor))
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          LukeSTM
      </td>
    </tr>
</table>

<pre>
    demo:
```
void __attribute__((constructor)) kkk2()
{
        __asm__ volatile ("":::);
}

void __attribute__ ((destructor)) foo()
{
        __asm__ volatile ("":::);
}
```

https://godbolt.org/z/7shvxT3hY

There are differences in the behavior of `__attribute__((constructor)) __attribute__((destructor)) ` between GCC and LLVM. GCC places functions with the `__attribute__((constructor))` attribute in the `.text.startup` section, and places functions  with the `__attribute__((destructor))` attribute in the `.text.exit` section，but LLVM does not. Why is this the case?



</pre>
<img width="1" height="1" alt="" src="http://email.email.llvm.org/o/eJysU01vpDoQ_DXNxQrytPk8cGAmj3dJTi96qz0hA83gHQaP7GaS7K9fwczuRkm0m0NQywi5uqvKlLX3Zj8RFRBvIb4N9MyDdcXdfKD_Hu6DxnbPRUdHC6oEWUIiryXLszWdqGvN7EwzM9U1YAaYtXby7OaWrQPMAXNxOBxw3cuXEekWZCmuT11rf6xrcbajZjOSWHG4lCqvhTmo7dp5u6zvMV_aso5eMffWfh7xC-8gy4H55FdUBVjtbdfYkUPr9oDVd8Aq9cP56UENXy_wh4EcCe1IdKbvydHUkhdmEjyQaGjQZ2OdsL2ARH7oUN8BvbEPiRQN8SPRJP7d7YSeOnF39_99uH6dRr1o6OepZWMnLx4ND6ueD2pYxv9C_fQCiQyZnjj0rB3PpwXkaWUAvEh4Q_w35tfG_kxMT4Zfsv5TwXYH2a6ZeXUvOkteTJZD8WV4FsYLHtaFRKs9gaouvwxkGXSF6nKV64CKTRopmclNlAVDsUmTSOVpghL7vKOsTXLdJblMKWlRyk1gCpQYS4XpBuM4ysI46Zu8lSrOW60URRBJOmozhuN4Pi65CYz3MxUbpTBKglE3NPr1ViJO9CjW3SWe8W3giqXpppn3HiI5Gs_-9xg2PFLxMmXvReBy5J-VtGB2Y_HqRhge5iZs7RGwWsRdXzcnZ79Ry4DVaskDVlfP5wJ_BAAA___ufGnX">